AI risk

jasonleow • 8 Mar 2026 •
I had said your dev job is safe, because for the layman, being able to doesn’t mean willing to. People don’t want to be devs.
But… that’s just for the layman.
For companies, AI is coming for your lunch, sadly. Layoffs due to AI are starting already, and they’re not even shy about it and blatantly stating it’s due to AI.
At the rate Claude Code and agentic engineering is improving, I’m not even sure I’ll be safe in my frontend dev job, similar to @knight says here. I use AI everyday in my freelance work, it writes all the code. So my added value is simply scoping the right task for it, curating the code, and catching architectural/syntax mistakes. Thankfully that’s still much needed today because for a large enough codebase, AI still tends to go ways off sometimes. Every day or every other day I catch it doing something it shouldn’t.
But looking at the trajectory, that could swiftly change in a few years. We already use it to plan and scope the work before the agent starts.
By that time, would companies that hire me still need devs when they can simply hire a AI who can do the work 24/7, never tires out, never falls sick, never needs to take a vacation?
I’m no longer confident I still have a job within the decade, tbh.
All the more reason to build my own thing.
Tl;dr - Write code for the layman, not for devs/companies.