I’m Shipping Like I Have a Team (I Don’t)
There’s this meme about a kid who got an angle grinder and it “changed his life” — the joke being he’s now cutting catalytic converters off cars. Dark humor aside, there’s a kernel of truth there: the right tool at the right time can completely change your trajectory.
For me, that tool was Claude with a Max subscription and a handful of CLI utilities. Over the past few months, I’ve built more software than I had in the previous three years combined.
The Setup
It’s not complicated:
- Claude Max: $100/month → now upgraded to the subscription with API access
- Claude Code: Anthropic’s CLI for agentic development
- Open Claw: Orchestration
- A handful of connected tools GitHub, file system, web access
That’s it. No massive infrastructure. No team. Just me, talking to a model that can actually do things.
What I’ve Built
iOS apps. macOS utilities. Web apps. Infrastructure for the Little League I help run. A podcast recording studio. Tools that solve problems I didn’t even know I had until building them became trivial.
I’m not going to list everything — that’s not the point. The point is that the list exists at all.
A year ago, most of these ideas would have stayed in my notes app. “That would be cool, but…” followed by all the reasons it wouldn’t happen. Too much boilerplate. Too many APIs to learn. Too many weekends I’d rather spend with my kids.
Now? I built walk-up music software for my daughter’s softball team because she asked for it. It’s in the App Store. She’ll use it at games. That sentence still feels surreal to type.
The Unlock
Here’s what changed: I stopped being the bottleneck.
Before, I’d have an idea, think “that would take a weekend,” and never start. Or I’d start and get stuck on some tedious part — API integration, UI polish, test coverage — and abandon it.
Now I describe what I want, iterate on the approach, and let the agent handle the mechanical parts. I focus on *what* to build and *why*. The *how* is a collaboration.
It’s not magic. The code isn’t perfect. I still review everything, fix edge cases, make judgment calls. But the ratio of “thinking about building” to “actually building” has completely inverted.
The Compound Effect
When building is fast, you build more. When you build more, you get better at describing what you want. When you get better at describing, building gets faster. It compounds.
But here’s what I didn’t expect: the *ambition* compounds too.
Projects I would have dismissed as “too much work” now feel approachable. Integrations I would have hand-waved away (“I’d need to learn that API…”) happen in an afternoon. The ceiling on what feels possible keeps rising.
This is what a new era feels like. Not a single breakthrough moment, but a gradual realization that the rules changed and you’re still playing the old game.
The Angle Grinder Parallel
That kid with the angle grinder? He suddenly had leverage. A tool that multiplied his physical capability dramatically.
This is intellectual leverage. I have the same 24 hours everyone else has, but I’m shipping like I have a small team. Ideas that would’ve stayed in my notes app are now real software that people use.
We’re at one of those inflection points that only becomes obvious in retrospect. The way we build software is changing — not incrementally, but fundamentally. The gap between “I wish this existed” and “I built this” is collapsing.
And honestly? I don’t think most people have caught on yet. A year from now, this will feel obvious. Right now, it still feels like a secret.
If you’ve been on the fence about trying AI-assisted development, just start. Pick a small project. Describe it clearly. See what happens.
You might be surprised what you can build with the right grinder.
Jake Spurlock builds things in the Bay Area. By day he’s a Forward Deployed Engineer at WordPress VIP. By night he’s apparently become a one-man software studio. He spends too much time thinking about baseball.
#development #iOS #MacOS #NerdyStuff #WordPress