02/09/2026
I recently read an article where a developer was worried that ๐๐ ๐ถ๐ ๐๐ฎ๐ธ๐ถ๐ป๐ด ๐ฝ๐น๐ฒ๐ฎ๐๐๐ฟ๐ฒ ๐ผ๐๐ ๐ผ๐ณ ๐ฐ๐ผ๐ฑ๐ถ๐ป๐ด โ and that developers are going to be replaced.
I completely disagree.
This argument feels familiar to me because Iโve heard it in every profession, including my own.
Iโm an accountant โ should I be worried that AI will replace me, too?
New tools donโt remove the joy of the craft.
They remove the ๐ต๐ฒ๐ฎ๐ฑ๐ฎ๐ฐ๐ต๐ฒ๐. (or create new ones๐)
Is the โpleasureโ really in:
โข Writing the same boilerplate code for the hundredth time?
โข Hunting for a missing semicolon for hours?
โข Repeating sequences that could be automated in seconds?
Or is the pleasure in building, thinking, solving, and creating?
I donโt find joy in unnecessary struggle โ especially when better tools exist.
And historically, thatโs exactly how progress works: we build tools to reduce friction, not glorify it.
I think the fear of โbeing replacedโ isnโt really about AI.
Itโs about being pushed out of a comfort zone.
Every industry faces this question.
Every generation does.
But hereโs the reality:
โข AI-written code is not perfect
โข Logic still needs to be reviewed
โข Architecture still needs human judgment
โข Debugging still requires experience
โข Accountability still belongs to people
Professionals with real expertise donโt disappear โ they evolve.
And if certain tasks are automated?
That doesnโt make you obsolete.
It gives you time to learn, to grow, to explore higher-value work.
Thatโs why I wouldnโt tell my kids, โDonโt bother learning to code โ AI does it now.โ
They still need to understand whatโs happening under the hood.
Because tools fail.
Power goes out.
Systems break.
And when they do, we still need people who actually know what theyโre doing.
AI isnโt taking the pleasure away.
Itโs taking away the busywork โ and giving us room to do better work.
Thatโs not the end of coding.
Thatโs the next chapter.
Peter N.
