There’s a conversation happening in every tech team right now. You can feel it in the room, even when no one says it out loud.

Is AI coming for my job?

I want to answer that honestly. Not with hype, not with doom. Just with what I actually see.

The Carpenter and the Nail Gun

A Paslode nail gun is extraordinary. What used to take a carpenter an hour with a hammer takes minutes. The precision is better. The fatigue is lower. The output is higher.

But here’s the thing nobody argues: the nail gun didn’t replace the carpenter.

It made the skilled carpenter dramatically more productive. And it made the unskilled one dramatically more capable of building something that falls down.

The tool amplified what was already there — in both directions.

AI is the nail gun. We are the carpenters.

The Problem I Keep Seeing

I’ve watched people struggle to solve problems for years. Not because they lack intelligence — but because they never learned how to look for an answer.

How to break a problem down. How to form a hypothesis. How to search effectively. How to know when you’ve found the right solution versus a plausible-sounding wrong one.

AI doesn’t fix that gap. It turbocharges it.

Give someone with strong fundamentals access to AI and they move at a speed that would have been unthinkable five years ago. Give someone without fundamentals access to AI and they ship confident, well-formatted nonsense faster than ever before.

The bottleneck was never the tools. It was always the thinking.

What This Means for Juniors

I hear a lot of concern about junior developers right now. That AI is closing the entry-level market. That there’s no room to learn on the job anymore.

I think that’s partially true — and mostly a symptom of something else.

If your value as a junior was “I can write boilerplate code,” then yes, that’s under pressure. But that was never where the real value was anyway.

The juniors who will thrive are the ones who understand why the code does what it does. Who can read an architecture diagram and understand the tradeoffs. Who know what a design pattern is solving for, not just what it looks like. Who can debug something they didn’t write.

AI can generate code. It cannot yet replace the understanding that makes code trustworthy.

The fundamentals aren’t a stepping stone you climb past. They’re the foundation everything else is built on.

So — Is AI Taking Your Job?

Honestly? It depends on what your job actually is.

If your job is executing known patterns without understanding them — then yes, there’s real pressure there. That’s uncomfortable but true.

If your job is thinking, solving, deciding, designing — then AI just made you significantly more powerful. Use it.

The nail gun didn’t put carpenters out of work. It raised the floor for what a single skilled carpenter could build.

That’s where we are. The question isn’t whether to pick up the nail gun.

It’s whether you know enough about carpentry to use it well.

What’s your take? Are fundamentals more or less important in the AI age? I’m genuinely curious — this is the conversation I want to have.