The best reaction to "this is confusing, where are the docs" is to rewrite the feature to make it less confusing, not write more docs.
@codinghorror @MartinDoms The best reaction is to do both. Self documenting code is a thing devs tell themselves to avoid writing docs.
@codinghorror @ID_AA_Carmack // #todo Apply to all human tools and knowledge.
@codinghorror @ID_AA_Carmack Yes, because rewrites always cure all problems!
@codinghorror Finding what requires a tortured explanation is a major benefit of writing docs: "It's easier to fix a crock than explain one"
@codinghorror as a developer, I would like simple user stories so I can write code to support them... pretty much sums that up eh?
@codinghorror @hnshah Easier said than done - who writes documentation these days?:)
@codinghorror @hnshah Easier said than done - who writes documentation these days?:)
@codinghorror Make it simple, not easy. And sometimes simple needs docs.
I don't agree to force people to read code to understand things. There can be high level docs. @codinghorror @ID_AA_Carmack
@codinghorror @ID_AA_Carmack My grandma doesn’t understand JSON, does this mean we all scrap it‽ Please say yes!
@codinghorror @ID_AA_Carmack Tell that to soap interface despite designers. They will give you devil's laughter, head thrown back
@codinghorror unless you're a tech writer and not a coder; then the best reaction is to write docs.
@codinghorror @jessenoller This "docs are hard, let's go shopping" bullshit has to stop.
@codinghorror @jessenoller Fix what's broken. If docs aren't sufficient to use a feature, fix the docs.
@codinghorror @jessenoller Many times, a feature is what you're looking for, if only you knew how to use it in ctx it was intended for.
@codinghorror I think you just described my entire coding career.