The Specialist Is Dead. Long Live the Product Builder.
The one-trick resume is a liability now. The generalist who ships just won the decade.
Real John here… This week, I’m talking about the generalist in the AI world. We are moving to a new paradigm. Something that is crazy cool, or simply crazy depending on your perspective. “Everyone can code” mentality is breaking the internet, and many engineering teams. I do believe everyone can use claude/codex/gemini to build a website. That does not mean you can code, it means you trust AI to be 100% right on what it produces because you have no idea on what it actually is doing. Engineers are becoming more valuable not because they can code, but because they can evaluate code.
I can have a 10 year old write better code from scratch than some AI. But that doesn’t mean AI is trash, it means it needs training, education. Engineers are the teachers/orchestrators/conductors now. We can do marketing, product management, financial analysis, and business gtm strategies. Oh, did that hit a nerve to you non-engineers? Why? Because you have spent your career learning the nuances of how to do your job that AI can’t possibly understand. Yeah, exactly. AI can augment you and automate the silly stuff, but you need to teach it how to be better. So engineers who are afraid of AI or worse, think it is AI slop, it is because you expect a 5 year old to be able to operate at a PhD level with no education. Give it the education, take the time to work with it, and it WILL be better than you shortly, and it will help you be better too! So we are not experts in an area anymore, we are empowered to teach it something that we imagine by having conversations, not by single-prompting and then expecting the first result be perfect. Ok, rant over for now… let’s get into this week’s newsletter. King of Spades this week, if you know you know. (Side note: I’m working on my Elmsley count and having a lot of fun with that)
When I was nine, I wrote BASIC on a Commodore 64. By the time I’d worked my way through a few jobs, I’d written ABAP, Pascal, C#, Python, JavaScript, Kotlin, SQL, and a pile of languages I’ve mercifully forgotten. I never set out to be a “polyglot.” I just kept needing to solve a different problem than the one in front of me yesterday.
For most of my career, that made me weird. The industry wanted specialists. “What’s your stack?” Pick a lane. Be the React guy. Be the Kubernetes guy. Be the one who only does machine learning pipelines and gets a little twitchy when you ask him to write a CSS file.
Well. Funny how that turned out.
The Org Chart Is Eating Itself
This isn’t me ranting into the void anymore. McKinsey just told a room full of engineering leaders the same thing: the high-performing teams are collapsing from the classic eight-to-ten-person “two-pizza” squad down to three-to-five people. Fewer specialists. More full-stack builders who can orchestrate AI agents across the entire stack — exploration, implementation, review — and own the whole outcome.
Read that again. The teams that are winning aren’t the ones with a specialist for every box on the org chart. They’re the ones with a handful of people who can do the whole job and point a few agents at the boring parts.
I have been screaming this for THIRTY YEARS. Great people beat big headcount. I wrote it when it cost me clients who wanted me to staff up. I said “I’d rather have $2 million for ten years than $5 million for one.” And now there’s a McKinsey slide that agrees with me. I’m not sure whether to feel vindicated or insulted.
Here’s the part nobody wants to say out loud: AI didn’t kill the specialist. AI just exposed that a lot of “specialist” roles were process overhead pretending to be expertise. When one person with Cursor and Claude Code can scaffold the backend, wire the frontend, write the tests, and ship to Vercel before lunch, the question “who owns the API layer” stops being a job title and starts being a Tuesday.
“But My Deep Expertise—”
Yeah, yeah. Calm down. I’m not saying expertise is worthless. I’m saying narrow expertise with nothing around it is now a liability.
The agent can write the SQL. The agent can refactor the component. What the agent CAN’T do is decide what’s worth building, catch the edge case that breaks production, own correctness end-to-end, or talk to a customer and figure out what they actually meant instead of what they said. That’s the human job now. That’s the WHOLE human job now.
If your entire professional identity is “I’m the person who writes the queries,” I have bad news and it’s already arrived. If your identity is “I’m the person who ships the thing that solves the problem,” congratulations, you just got a raise nobody told you about.
I built Cash Critters for fifty bucks a month. One person. The whole thing — finance app for kids, real users, real product. I am not a designer. I am not a DevOps “guru.” I’m a builder who refuses to be precious about which part of the stack he’s allowed to touch. That’s the entire move.
What To Actually Do About It
Enough theory. You came here for something you can do, so here it is:
Pick the part of the stack you avoid — and go build something in it this week. Backend person scared of CSS? Build a UI. Frontend person who fears the database? Stand up a schema. The fear is the map.
Stop collecting tutorials. Start orchestrating agents. Open Cursor or Claude Code, give it a real task, and learn to review its diffs like a hawk. Your job is judgment, not typing.
Ship one end-to-end thing with your name on the whole thing. Idea to deployed. No handoffs. No “that’s not my area.” Own all of it once and you’ll never go back.
Delete “I only do X” from how you describe yourself. You’re a problem solver who happens to use code. Say that instead.
The specialist waited for the perfectly-scoped ticket. The product builder just asks “what’s the problem?” and goes.
The thing is, I never had a choice. I learned to do all of it because I was usually the only one in the room, or because nobody else would, or because the Commodore didn’t come with a team. Turns out the constraint was the gift. It always is.
The whole industry is finally being forced into the corner I’ve lived in my entire life: be a generalist who ships, or be a line item that gets optimized away. I know which one I’d pick. You already know too.
So stop guarding your little patch of the stack like it’s a kingdom. It’s not. The kingdom is the thing you ship.
Now go build something amazing — all of it, this time.
Final note: (still real John)… Most people don’t need another podcast, book, or AI tool.
They need a room full of people who are actually building.
My next Barn Session is happening in July. Six to eight people. One weekend. Real conversations. Real accountability. Real progress.
If you’ve got an idea that’s been living in your head for too long, let’s talk.
John Mann is the founder of Startups and Code LLC, a software engineering executive, and the guy who built Cash Critters for $50/month because constraints are a feature, not a bug. Subscribe for weekly takes on AI, startups, and building things that matter.