CTOs warn: “AI can help, but if you stop thinking for yourself — this job is not for you.”
If I were a junior developer starting out today, I’d probably be quite confused. With AI tools increasingly taking over the process of writing code, is learning how to program still enough? Or is this profession gradually being handed over entirely to AI assistants?
These questions are becoming more common — and for good reason. In 2024, European tech companies cut junior developer positions by 72%. Despite that, many tech leaders share the same view: AI won’t kill the profession — but it will leave behind those who can’t adapt to working with it.
“Learn to think, not just to code”
Emanuelis Norbutas, CTO of nexos.ai, breaks it down simply:
“Being a good developer today means more than just knowing Python or Java. You also need to understand how AI models work, where their limits are, and how to design effective prompts.”
AI tools are powerful assistants. But they can also be unpredictable — producing illogical, erroneous, or even completely fabricated code. That’s why the fundamentals — algorithms, systems architecture, debugging — remain just as critical as ever.
“AI can write the code — but the problem is still yours”
Marijus Briedis, CTO of NordVPN, speaks candidly:
“If you can’t review and validate the code AI generates, then you’re the problem. A developer still needs to test the code, understand what it’s doing, and ensure it’s secure.”
Georgie Smallwood, CTO of Moonpig, points to another crucial concern: the source of AI-generated code is often unclear. This introduces serious questions around security, intellectual property, and copyright.
“AI will give you code. But who actually owns that code? Is it safe? Will it run reliably? These are questions you cannot afford to leave unanswered.”
Three key tips from CTOs
1. Try solving the problem yourself before turning to AI
Smallwood says:
“I always tell junior developers — try to solve the issue on your own first. If you run to an IDE or an AI assistant in the very first minute, you’ll never develop the mindset real engineers need.”
2. Finish your projects — don’t just write code, deploy it
Writing code is just the beginning. Deploy it. Watch what breaks. Analyze how users respond. That’s what shapes a true engineer.
3. Learn to think — and communicate — in writing
Developers don’t just work with machines — they work with people. Your code needs to be understood by others. And that depends on your ability to explain your logic clearly and document it well.
“Why does this work?” — the most important question
CTOs agree on one core idea: AI is a powerful tool, but it won’t think for you.
Your ability to ask critical questions, spot mistakes, analyze code, and communicate clearly is what will set you apart.
A great engineer isn’t just someone who codes quickly — it’s someone who questions, tests, and, if needed, rebuilds from scratch.
Conclusion
If you rely too heavily on AI, it will eventually take your place.
But if you learn to collaborate with it — to think independently and use AI as an extension of your skill — then it will become your greatest amplifier.
Prepared by Ismailova Laylo
