One 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 p

One 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.