What if the code you crank out solo rivals a 10-person team’s output—and nobody notices?
That’s the nightmare fuel for builders like Estyn Software’s founder, who’s finally spilling the beans online. He’s not a content machine. Far from it. But building at team-scale alone? That’s the game-changer forcing his hand.
I’ve seen this movie before. Remember the early days of indie game dev? One guy in a basement ships a hit like Flappy Bird. No team. Pure grit. Now AI agents—hooked into Jira, GitHub, AWS—are handing that use to enterprise coders too. Barriers crumble. Not ‘cause work’s simpler. use explodes.
Estyn’s guy nails it:
The rise of AI agents that can interact with real engineering toolchains — Jira, GitHub, AWS, the lot — means that a single person with the right experience and judgement can produce work that used to require a team.
Spot on. Except—here’s my twist, the one he doesn’t hit—the parallel to 1990s shareware kings. Back then, a floppy disk demo got you discovered. Today? It’s a ghost town without visible thinking. No blog, no threads, no visible process? You’re a talented hermit coding in the dark.
Why Can One Dev Suddenly Match a Team?
AI agents aren’t magic pixie dust. They’re glue. They navigate toolchains we built for squads—pull requests, CI/CD pipelines, cloud deploys. One person orchestrates it all.
Estyn’s building Porth, a common component for integration projects. Why build, not buy? ‘Cause off-the-shelf crap doesn’t flex. He’s journaling the guts: architecture calls, AI workflow wins, brutal limits. Two years ago? Laughable. Today? Routine for the skilled.
But don’t kid yourself. Judgement’s king. AI spits code. You pick winners. Miss that, and it’s garbage at scale.
Short version: use is here. Use it.
The catch? Bottlenecks migrate. Fast.
Is Visibility the New Dirty Word for Builders?
Here’s the gut punch:
If you can build at team-scale as an individual, the bottleneck shifts. It’s no longer about whether you can do the work. It’s about whether anyone knows you exist.
Oof. He’s right, and it stings. Us introverted types? We’d rather ship silent. Let code scream. But markets don’t care. In this flood of solo firepower, the visible win. Not schmoozers. Documenters.
Your portfolio? Dead CVs gather dust. Now it’s living proof: threads on decisions, mistake autopsies, process playbooks. Estyn’s betting on honesty over polish. Smart. Bland tutorials? Yawn. Raw journey? Hooks clients.
And yeah, it’s PR spin risk. Companies hype AI as free labor. Truth? It’s amplifier for pros. Amateurs flail. That’s the divide.
Look, I’ve covered toolchains for years. This shift echoes open-source booms—Linus alone tamed kernels, but GitHub visibility exploded adoption. Prediction: we’ll see a new underclass of invisible talent. Ghost builders shipping gold, starving for gigs. Don’t join ‘em.
But—dry humor alert—now you’re coder, architect, marketer. Joy.
Estyn’s not preaching. He’s wrestling reluctance publicly. Relatable as hell. If you’re that quiet killer in the corner, peeking at his series might nudge you online.
Skeptical take: AI agents hyped to godhood? They’re clunky toddlers still. Hallucinate tickets. Botch merges. But iterate fast, and team-scale solo becomes default. Estyn’s Porth proves it—real enterprise, not toy apps.
What works? Tight loops: prompt, agent runs toolchain, you judge, repeat. What flops? Vague specs. Garbage in, garbage out.
Does This Kill Teams—or Supercharge Them?
Teams won’t die. Nah. But expect shakeups. Mid-managers? Sweat. Architects with visibility? Thrive.
Unique angle: think aviation’s golden age. Solo pilots barnstormed pre-WWII. Daring feats, newspaper ink essential. No press? Forgotten. Tech’s there now. Your Porth-equivalent needs a megaphone.
Hype callout: consultancies like Estyn spin ‘digital transformation.’ Cute. But solo use exposes fluff. Real value? Visible execution.
So, start shipping thoughts. Blog. Threads. Whatever. Or watch louder mediocrity lap you.
Punchy truth: hide, and you’re done.
This isn’t optional anymore. It’s survival.
Rare builder admits it publicly. Props to Estyn. The rest? Lurking, losing.
🧬 Related Insights
- Read more: Power BI’s Data Frankenstein: Stitching Sources Together Without Screaming
- Read more: Claude Code Unleashed: Config Tweaks That Turn Senior Engineers into Superhumans
Frequently Asked Questions
What does ‘build at team-scale alone’ mean?
It means one dev, armed with AI agents, outputs software volume and quality that once needed a full squad—think Jira flows, Git commits, AWS deploys, all solo.
Do I need to blog if I’m a solo developer now?
Yeah, probably. Visibility’s the new bottleneck. Document your process, or stay invisible amid the AI-fueled solo boom.
Are AI agents ready for enterprise work?
Close. They handle toolchains well but need sharp human judgement. Limits exist—hallucinations, edge cases—but they’re dropping fast.
