Skip to content
AI-assisted engineering

Implementation is free. Taste is the bottleneck.

I deleted all the repos and rebuilt shareful.ai from scratch in one night with CC Max 20x. Had it live before morning. That is not a flex. It is a datapoint about how dramatically the effort-to-outcome ratio has changed for side projects.

Based on my January 2026 Startmate session on Claude Code and shipping fast, and drawn from projects shipped between late 2025 and early 2026.

Three keystrokes and the swarm spins up

I have a Raycast snippet called "zcc." Three keystrokes expand to my standard Claude Code prompt: "Do extensive research. Make a plan with phases and todos. Use a swarm of subagents and teams." That is how most projects start.

The setup is intentionally low-ceremony. Zed editor, multiple terminals, Claude Code doing the heavy lifting. For personal projects I yolo to main. No staging branches, no review queues. The goal is to reduce the distance between idea and live product to near zero.

The time excuse is gone

308 GitHub repos and counting. Not all of them are winners, but every one tested a different assumption. The constraint has shifted from implementation ability to taste, context, and the willingness to start over.

That shift sounds liberating. It is, mostly. But it also means you cannot hide behind "I did not have time to build it." The time excuse is gone. What remains is whether your idea was any good.

Speed without direction is just motion

When building is cheap, the only question is whether what you build feels considered. The tools make shipping trivial. The hard part is deciding what deserves to exist.

I keep coming back to that. The people building the most interesting things right now are not the fastest coders. They are the ones with the clearest sense of what matters.

Keep reading