Comment by keithnz
17 hours ago
Same, I've been coding for 40+ years, and other people I know of similar length of time also seem real quick to adopt AI. I'm constantly having to show the young devs how to get the most out of their AI agents and also adapting my workflows regularly as things changes. Weirdly its some of the youngest who are most resistant, I think because they are learning coding skills, and just have got the hang of coding such that they are productive, and AI is coming in and taking that away from them largely, they are still keen to code. While I've enjoyed coding, realistically it's always been the bottleneck in creating software. A lot of the process is about how to effectively manage that bottle neck, now a lot more options are available. Iterating quick, trying different things, experimenting. Much easier to throw something away when you have better ideas.
I've been coding for 25 years now, and it's not that I see AI as evil, but more that it doesn't solve any of my problems or looking back, any problems I had at previous roles.
It's always been someone higher up the ranking wants meetings, training or something dumb because his golf buddy sold him on Kafka support contracts in inappropriate situations, or an architect needs to shoehorn some tech in so they can have it in their designs ready for their next job role. I spend probably more time in meetings than doing coding.
Why can't I have an AI that takes my meetings for me?
I started with x86 assembler and Turbo Pascal (I still remember when I got documentation for Turbo Vision - this was groundbreaking!).
The simple truth is that I had to constantly learn something new and this is how it is in this profession. We’ve been in the trenches and we did it over and over again.
Now I’m using AI full time, doing same thing I always did - shipping products.
Newcomers with first set of skills don’t understand what is meta responsibility in this field - it’s never coding something, it’s shipping products to solve business needs.
As a "young" coder I am hesitant because I don't have decades of skills to fall back on.
It is even more abstraction, even harder to follow the code I'm "writing" with AI.
Also I have a fear that if/when the AI tide recedes, I'll be the one caught with my pants down since I have been forced to vibe code the majority of my career. As opposed to greybeards who can fall back on their decades of knowledge.
You nailed it. Only option is to build skills, preferably on company time. Just remember there's a lot of mediocre devs, and you probably have more time than you think to do things.
I'm about the age where I need a walking stick and a cyborg arm to keep up with all these leetcode artists. AI couldn't come at a better time.
I've been around the block and I feel the same.
The best complement to AI will be a human who is part architect (they know not to build the new system on lovable, and they understand the company's digital assets) and part business analyst (can communicate effectively and tease out and distill requirements from customer team).
That indicates someone who has top notch communication skills and also quite a bit of experience i.e older.