[Too]

Good resource. One common flaw i see in many technical writings, which i missed from the course, is treating the reader as a complete puppet. As in giving copy-paste instructions on what to do, but not explaining what's happening underneath.

Better to teach a man how to fish than giving away a fish, or better condensed by Fred Brooks famous quote from Mythical Man Month: Show me your flowcharts and conceal your tables, and I shall continue to be mystified. Show me your tables, and I won’t usually need your flowcharts; they’ll be obvious.

[ghaff]

To be honest, that's a problem with a lot of in-person workshops and the like as well. There's a lot of type this, type that, run this script, etc. without enough context as to why you're doing these various steps.

[ntsplnkv2]

Yep - so many workshops could simply be a list of steps to do X. But often times the real world isn't that simple, and then the workshops are essentially worthless. With an understanding of how something works, I can apply it to more scenarios, or modify it to fit more scenarios. This is often woefully lacking in modern training/documentation.