I was looking at results of the Stackoverflow Developer Survey 2025, and one aspect caught my attention: the percentages relating to developers' co...
For further actions, you may consider blocking this person and/or reporting abuse
I really appreciate your delineating the classic, romantic and pragmatic developer types! I've never thought of that before, but I can definitely see those 3 types. I confess that I've seen the romantic developer in myself, more than I care to. But I've also seen the pragmatic developer in me, too. Which I am glad for.
And FWIW, I loved the book Zen and the Art of Motorcycle Maintenance.
Thank you for your feedback!
The number of people who vote for not trusting the ai tools surprised me, because there are so many people who are posting about their awesome vibe coding experiences.
They just share their experience, which is indeed vibing. That does not mean that this is the experience that allows you to get working and secure code ;-)
Blowhards on Twitter aren't representative of most developers, though. Neither are respondents to StackOverflow surveys necessarily, but they're probably closer to the mean.
Developers who practice test-driven development should have a major advantage moving forward with AI. I suspect that writing prompts with tests included may produce better initial code. As for me, after 20+ years in development, I shifted a few years ago to working with deployment pipelines, ansible, kubernetes, etc. I'll likely make another shift before retiring...likely to woodworking.
Unless they leave it to the AI to create tests for the code it generates, of course :-)
That would be a great achievement! :D
I wasn’t really familiar with this way of categorizing programmer types, but I’ll definitely look it up! The way you explained it was super interesting.
Your points made a lot of sense and the comparison clicked right away. Overall, really smart insights and reflections backed up by real data on the current scene.
Also, the quote "The Developer Is Dead. Long Live the Developer." is awesome
Thank you!
"We cannot afford to be romantic developers who blindly trust the code generated by AI tools. " - Accurate!!
Thank you!
I am a pragmatic developer with a bit curiosity of a classic developer sometimes. I totally agree on not trusting the AI generated code. I use them but always after a verification step.
“AI as copilot..not autopilot” .. Love this take
"I identified three types of developers:"
Realy interesting. I can see myself flowing arround the 3 types, depending on the project and on my dayly mood. Thanks for the article!
Thank you for your feedback :-)
Vibe coding without knowing how the code will run might be troubling, as future bugs and security risks hit hard :-D
I love and appreciate the fact that you don't dismiss vibe-coding and also see the reasoning of why we still need classical coders. Well spoken and written. Cheers!
Thank you! ❤️
Hmm - I mean yea in general you should not trust it - but I would hesitate to say never. It's just getting more and more reliable - and the smaller /more specific the prompt the more likely it is that you can trust it'll make the change you wanted. I do check nearly everything it writes, especially large changes but becoming more confident with its changes as I improve it's guidelines like CLAUDE.md .
It sounds like you're saying you trust it after verifying it. That's exactly what I'm arguing in this post. Human verification is always necessary.
A code-generating AI tool is not a deterministic tool, like a traditional compiler, for which there are formal verification techniques that let you sleep quite peacefully :-)
What about scanners then? I see a lot of Dev Sec Ops running them and some are AI based. I mean I even use Ampliy's and it still depends on me. Wait I see what I did there. Andrea you are so right. lol - facepalm
As with any other tool, the final decision is yours.
An AI scanner helps you to find more issues than an ordinary scanner, but it helps you. It does not make any decision :-)
I think it's still better to use Python
For all these reasons, LLMs should be prohibited for juniors and below.
They have insufficient knowledge to assess risks and problems.
I wouldn't say they should be prohibited. When used correctly, they can be effective learning tools. I mean, no worse than googling and copying/pasting from Stack Overflow :-)
I see your point. But some tools are actually helping juniors so seniors who cannot train them, have back up for their efficiency. I guess it depends on the dev though, and the context of what they're building?
It definitely depends on the dev and perhaps the context. AI tools can certainly help junior developers by showing them how to solve a specific problem or implement an algorithm. However, in my opinion, they should always try to understand and verify the generated code with a senior before using it in production. This is an opportunity to learn.