| I’m going to be less sympathetic than others here and say this is a “you” problem. Technology does change over time, as you say. Some of these changes are good, and some bad. Some useful technologies and techniques develop. Identify the ones which offer you a benefit, and reject the ones that don’t. This is one of the core competencies of a good software engineer. If you find yourself thinking “everyone is an idiot except for me” then it’s a signal to take a step back and reflect. There are reasons that engineers embrace various different technologies. Some of them are good - technologies that provide some great benefits and which are applicable to the work you do. Others are bad reasons - including trendiness or ignorance of existing solutions. Finding yourself dismissing popular technologies out of hand—rather than being genuinely curious about how they can be used—is a sign that you have stopped thinking with your engineer’s hat on. And I understand that this can be hard to overcome at times. There is nothing wrong with you having deep knowledge in a set of reliable technologies; there is something wrong in assuming there are no benefits to other approaches. I will also point out that: 1. Many engineers in the early 2000s would have accused you of being a “cursed” software engineer for picking up a trendy new pointless technology like Java. Reflect on that. 2. Amazon has been providing cloud services for 20 years already. AWS as a distinct entity has been around since 2006. It most likely will be here in 20 years. 3. If you think the trades remain static you’ll also be surprised there. Tools, building materials, and techniques also change over time. Not to the extent that they do in newer industries, but also way faster than you’d think. |