4 ms·
A lot of negativity for this article, but it addresses something I often see in those just starting out: searching for help in an overly specific way. You'll f
by michaelbuckbee 9y ago
A lot of negativity for this article, but it addresses something I often see in those just starting out: searching for help in an overly specific way.
You'll find people asking: "How do I create on online store for my candle making shop?" and you'll point them to a tutorial that happens to use a shoe shop as an example and they'll think it doesn't apply to their situation.
The article's advocating for people to use tutorials as a jumping off point, to ask more specific questions and to reason through what does and doesn't apply to their situation.
Also, fwiw - hats off to the many, many tutorial writers whose articles have helped me over the years.
- breeny592 9y agoOne of the most valuable skills I always try to teach junior (and sometimes not so junior) developers is not only how to abstract your problems (as the author points out in this article), but also how to follow a related chain. For instance, let's say you have an issue with some event not firing in an old browser, and as you research it, you see the same answers saying a concept you haven't heard of before. Looking that concept up (and either reading about it or following some tutorial) then teaches a wider understanding in that domain, instead of a bandaid fix that the developer doesn't understand but fixes the problem now. The role of a developer isn't just about solving problems, but to understand why the solution works as well.