Expectations were simple: nail the code, ship fast, scale solo. That’s the solo founder gospel, right? Pump out APIs, workflows, security layers with AI sidekicks like Claude — and watch the product hum.
But yesterday? Reality slapped back. Tobias Lütke — wait, no, this Tobias running ConnectEngine OS — cracked open his master plan. Phase 6 and MT? Duplicates. Phase 3? ‘Not started,’ despite production glory last week. Dependencies ghosted. Stale status lines everywhere.
Code? Immacaculate. Linted, tested, deployed. AGENTS.md? Living truth. The villain? Plans.
The code was accurate. AGENTS.md (my living reference file) was accurate. The rot was in the plans themselves.
That’s the killer quote. Plans lack linters. No CI/CD for roadmaps. They drift — quietly, like mold in a fridge you forget to check.
Why Do Plans Rot Faster Than Code for Solo Founders?
Teams catch this crap daily. Standup hero pipes up: “Wait, shipped that last sprint.” PM cross-checks. But alone? You’re the coder, PM, QA — all in one meatbag. Plans only surface when you’re sprint-starved, already three weeks stale.
Market dynamics scream louder here. Solo founders fuel 40% of SaaS startups now — per CB Insights data — chasing AI agent gold. ConnectEngine OS? n8n-powered beast for unsexy infra: RLS policies, tenant isolation, 2am error recovery. Everyone expected bulletproof code to carry it. This flips the script: docs can tank you faster.
Here’s the thing. I see echoes of the 90s dot-com bust. Back then, VCs funded vaporware on glossy specs — plans untethered from code. Solo today? Same trap, self-inflicted. Your brain anchors to fiction, priorities warp.
Tobias didn’t patch. Trap. He researched first.
Claude dumped inventory: 85 API routes. 49 tables. 24 security funcs. 15 workflows. 16 plans. Grounded in code, not memory fog.
Then sequential read-through. Not parallel — that’s for suckers. Back-to-back? Overlaps jump: Phase 6 credential mgmt and MT notifications? Same DB pattern. Merge. Boom, saved scaffolding sprint.
Multi-tenant audit? 16 items, 10 dupes. Folded ‘em. Security bug? Nested into merge.
One commit. 22 files. +893/-288 lines. Canonical list now — source of truth.
Plans had dozens of lies. Code? Zero.
And my unique callout? Corporate hype ignores this, but here’s the prediction: by 2026, AI agents like Claude will ship plan linters as default. Diff roadmaps against repos automatically. Solo market demands it — or watch 30% more projects stall on misprioritization.
How Did He Actually Rewrite Without Anchoring to Lies?
Process locked in. Pre-rewrite: dump system state. Compare to facts. Sequential scan for merges. One commit per session — diff narrates.
Decisions warped on yesterday’s system view. “Phase 3 not started”? Mental block, even in prod. Stale second brain poisons every choice.
Solo stat: 70% fail from execution drift (Y Combinator lore). Plans are your proxy team. Rot ‘em? You’re fighting ghosts.
But look — n8n choice was genius. Delegated team work to workflows. Same for plans: automate review.
When’d you last gut-check your roadmap? Full read, plan-by-plan, vs. live code?
If ‘don’t remember’? You’re rotting too.
This rigor hit infra logs first — security nightsweats. Now plans. Won’t stop.
Market shift: AI dev tools boom, but solo pitfalls widen. Tools like Cursor, Claude code — they lint code. Plans? Your gap.
Fix it. Or drift into irrelevance.
What Happens If You Ignore Plan Rot?
Production ships, users love. But next phase? Chasing phantoms. Dupe work. Missed merges. Burnout spikes — solo tax.
Teams mitigate via friction. You? Engineer it out.
Bold stance: don’t just read. Rebuild. Facts first.
**
🧬 Related Insights
- Read more: Shelfy’s PySide6 Migration: Python’s Answer to Desktop App Bloat
- Read more: AI-First Apps Obliterate Frontend’s Sacred Rules
Frequently Asked Questions**
When was the last time solo founders checked their roadmaps? Most never — or not fully. Stale data leads to bad priorities.
How do you lint plans like code? Dump repo inventory via AI, read sequentially vs. facts, merge dupes in one commit.
Will AI tools fix plan rot automatically? Soon — expect linters in Claude/Cursor by 2026 for solo devs.
