3 ms·
I've umm'd and ah'd over this as well, thinking it'd be a good idea to have a structure to learning by basing it around teaching others - and then I think about
by wastedhours 8y ago
I've umm'd and ah'd over this as well, thinking it'd be a good idea to have a structure to learning by basing it around teaching others - and then I think about the number of tutorials I've gone through, only for the last paragraph be "obviously, that's not how you'd do it in production" with no next step and wanting to punch the screen.
If you're going to teach things, make it actually work for what the person reading needs. Personally, the chances of me reading a tutorial for interest vs wanting to accomplish a task are minimal.
Tutorials for learning, articles for interest. I'd say you could do the latter without expert knowledge, but the former needs to be pretty tight.
(All of this with the knowledge that imposter syndrome is so prevalent that we don't want to put off technically brilliant people writing tutorials when they think they might not be up to snuff).
- golergka 8y agoTutorials are for getting quick bootstrap on the platform. If you want to learn how do something in production, there's usually a manual or official user guide in place.
- wastedhours 8y agoBut why would you want to bootstrap your knowledge on something detached from your actual use case? Lots of people on HN bemoan the lack of formalised education and crappy code stitched together, but that's what half arsed tutorials and impenetrable documentation breed.