2 minute read

It’s just past a week since I started developing with Claude Code.

I think I started out of curiosity — how far can I get with this?

First a simple website, then app + server, then app + server + admin, then a simple auth service + push service + app + admin + payment service + analytics…

…and now I’m building an enterprise-grade server laid out as microservices.

What I’ve felt while using Claude Code is this: you have to be solid on the fundamentals.

Seventeen years working as a developer. I entered a computer science program in 1999, so counting from then it’s been 26 years.

They say nobody is hiring juniors right now. I understand the reasoning well enough. In the old days, when a project came in and it was large, you staffed it accordingly — a PM, a PL, and so on. Now there’s no need for that. In their shoes I’d hire only a PM or PL who handles Claude Code well. The PM draws the broad architecture and the scenarios, and if you write out the architectural flow to match those scenarios and describe where and how the data gets stored, that covers it.

But is it really true that building a system means juniors aren’t needed? Building the system matters, and so does operating and maintaining it.

If you keep assigning PM- and PL-level people to operations and maintenance, there is no bigger waste of efficiency. And yet — could a junior who doesn’t even know how it was built in the first place take over operations and maintenance?

Yesterday I happened to talk with two CEOs running development teams at small and mid-sized companies. They aren’t hiring juniors, and they’re thinking of letting go the ones they have.

The junior you train now becomes the PM or PL of the future. For a project of that size, I’d attach at least two juniors, and they’d need to understand the architecture, the data flow, the data lifecycle — and on the frontend, state management, sync/async handling in the UI, call ordering across lifecycle events. Without that, they can’t even maintain it.

When I hear “AI does the coding, so they can spend the leftover time on operations and maintenance,” I get a strong sense that something is going wrong.

And this is only the beginning of vibe coding as a technique. Claude Code, Skills, Plugins, Google Antigravity, Cursor… so many technologies coming out. I’m studying day by day too, going “oh, there’s this as well” and trying things out.

Day to day, I’m happy just playing around with Rood.

Just scribbling while our Rood is at work.

Updated: