Software Engineering After AI: Disruption, Not Displacement
It took me a while to admit that the craft I spent years building might no longer be the most relevant thing about me.
I’ve been a professional software engineer for eight years and have been coding for more than a decade. I’m confident in my tools: Node.js, web servers, REST APIs. I’ve built data pipelines, web apps, backend services, and integration systems by hand, and I took real pride in that work.
This blog is going through a few changes.
I have been thinking about writing this for a while. Reading my blogs from this year, you must have seen a shift in content. Most of the writeups are not about the how-tos and whats of technology but mostly my opinions about it. Most of my energy went to communicating my feelings and understanding working with AI. I do not want to make this blog all about AI, but currently that is what I spend most of my time with.
In 2026, I have hardly produced any code that was not generated by AI. Models like Claude Opus 4.8 and GPT 5.x, along with agent harnesses like Codex and Claude Code, made it extremely easy to generate production code.
So much so that people started throwing around ideas like “coding is a solved problem” and “code is cheap.” I disagree. I think we have simply moved a level of abstraction up.