DEV Community

Discussion on: The slow and painful death of a developer

Collapse
 
webreaper profile image
Mark Otway

There are elements to this that are true, but part of it is also a fallacy. Why? Because no matter how much we like to think new tech is different, it's often not. The saying goes, there's nothing new under the sun. I've worked in tech for 25 years, and been dabbling with programming for 35 and can safely say that there is very little that is revolutionary or groundbreaking. Some of it is a bit different to tooling or processes that have gone before, but if you're a competent developer, transition should be easy.

Good example: in 2004 I had an interview for a C#/.Net role. I'd never even seen C# before; my previous 10 years were C++. I spent two days learning C# over the weekend and aced the interview on the Monday.

The main skills you need for a job are to be able to communicate with your stakeholders and team members, to prioritise your time, and to be able to learn stuff reasonably quickly. Trying to get into a hamster-wheel of feeling like you have to learn every new technology that comes along to stay up to date means you're on a hiding to nothing, and will simply exacerbate your imposter-syndrome affliction.