(OP link is worth a read btw despite how heavy it is presented, btw) This post articulates a bug-bear I've had throughout my career which is the pedantic "RTFM

(OP link is worth a read btw despite how heavy it is presented, btw) This post articulates a bug-bear I've had throughout my career which is the pedantic "RTFM" culture in software - where no one wants to help anyone and instead gives them a pointer to a document (the 'Descriptive Process" as the author describes it). Proscriptive Process, actually sitting down with someone(s), not only is valuable for the reasons the author suggests (re-examining process, updating, refining, improving) but often new issues and idea and opportunities emerge from going over something together or in a small group. Sure, you can't do it all the time but there are loads of examples when it is valuable and should be considered part of the cost of development. I think it's sad when you enter a workplace where everyone just wants to tell you to RTFM all the time and no one has the time to sit down and go over anything. Ultimately, I don't believe its how good product/software is made.