Senior dev confession: I asked Copilot to write a function yesterday. It wrote it. It worked. I stared at it for 10 minutes trying to figure out what it did.
This is the new senior dev experience. We don’t write code anymore — we interrogate it. “Why did you use a Map here?” “What’s this regex doing?” “Are you sure this isn’t going to delete the database?”
Honestly? AI made me a better engineer. Not because it writes good code (it doesn’t, mostly), but because reviewing AI code is like reviewing a junior who never gets tired and never takes feedback personally. My code review skills have never been sharper.
The job didn’t disappear. It just shifted from “writing” to “saying no, do it again, but this time without the security vulnerability.”
Anyone else feel like a tech lead for a robot? 🤖

Luis Cruz

A senior developer reflects on how AI coding tools like Copilot have shifted the role from writing code to reviewing and interrogating AI-generated code. Rather than replacing the job, AI has transformed it into something resembling tech lead oversight of a tireless junior — sharpening code review skills in the process.

"AI in my workflow" angle

I also think AI-assisted coding has increased the volume of codebases significantly, while many developers are not reviewing the generated code deeply before pushing it.
The problem is that AI scales code generation much faster than human understanding and review capacity. That can easily lead to poorly understood abstractions, duplicated logic, and long-term maintenance overhead.

In the era of abundancy of code, the true new scarsity (the actual choke point) will be the ability of validating and testing the new features and the software itself.
Human intervention is now shifting down the value chain where expertise and experience might allow to easily and swiftly validate products while minimally touch the code base