Noticed the same pretty early here too. My response was to categorize all tech into ephemeral implementations and more persistent concepts. The latter moves a lot slower. New fundamental ideas just don't come around as quickly as people writing their own take on them or combination of them. Some paths through SE make this easier or harder, i.e. being a front-end dev can easily have you drowning in library churn and simply without the time for any deep thoughts.
It's definitely an important factor to both notice at all and your decision in regards to it has lasting repercussions. In my experience, the majority of devs don't take the conceptual path, so I've tended to let them get excited about NewFancyLibrary and while I focus on more abstract things like architecture, modeling systems, and languages. Seems to work pretty good, since we're both happy with the arrangement.
Comments
Noticed the same pretty early here too. My response was to categorize all tech into ephemeral implementations and more persistent concepts. The latter moves a lot slower. New fundamental ideas just don't come around as quickly as people writing their own take on them or combination of them. Some paths through SE make this easier or harder, i.e. being a front-end dev can easily have you drowning in library churn and simply without the time for any deep thoughts.
It's definitely an important factor to both notice at all and your decision in regards to it has lasting repercussions. In my experience, the majority of devs don't take the conceptual path, so I've tended to let them get excited about NewFancyLibrary and while I focus on more abstract things like architecture, modeling systems, and languages. Seems to work pretty good, since we're both happy with the arrangement.