"Should we rewrite?"
Usually no. But "usually" isn't a plan, and a rewrite on a hunch burns six months.
The Vibe Coder's Guide to Software Architecture
You built it with AI. Now understand what you own.
I read the code your AI wrote, map the system you actually shipped, and tell you what to keep, what to fix, and what to leave alone, before you rewrite, hire, raise, or scale.
Risks surfaced: 0/6
Move the lens
Drag the lens over the app. The dashboard is what you see. The X-ray is what you own.
Comprehension debt
Every prompt ships code. Not every prompt ships understanding.
Illustrative. Your curve is different. The shape usually isn't.
It compounds.
Each feature built on an unexamined assumption makes the next change more expensive. The agent doesn't slow down. The debt doesn't either.
It stays invisible until it's urgent.
You meet it during an outage, a security questionnaire, a diligence call, or your first engineer's first week, when "we should rewrite this" gets said out loud.
It's cheapest to pay down today.
Not because today is special. Because every day after it, there's more to understand.
Today, your codebase is the smallest it will ever be. That's the best time to read it.
Select your level
The big decisions arrive on their schedule, not yours.
Each one is expensive to get wrong and cheap to get right, if you understand the system when it shows up.
The first engineering hire
The system you own decides the engineer you need. Hire for the wrong system and you hire the wrong person.
The enterprise deal
SSO, audit logs, tenant isolation, and a 200-question security review, due before the contract is signed.
The fundraise
Technical diligence asks questions about your system. You want to have heard them first.
The launch spike
A good launch is a load test you didn't schedule. Know where it bends before the traffic finds out.
The slowdown
Every change breaks two things and nobody knows why. That's an architecture problem wearing a productivity costume.
The offer
One product. One decision. A plan you can act on.
Architecture Risk Audit
A fixed-scope audit of your AI-built product, aimed at the decision in front of you, with a clear answer at the end.
- Scope
- One primary decision plus up to two critical workflows, like signup, billing, or data access.
- Timeline
- Five business days once scope, start date, and read-only access are agreed.
- Who it's for
- Founders and solo builders with a working product, real users or funding, and a consequential decision coming up.
- Capacity
- One active audit at a time. You get my full attention, and the next founder waits.
Inventory: what you receive
System map
How your product actually works, drawn so a new hire or an investor can follow it.
Ranked risks, with evidence
What could hurt you, in order, and where in the code it lives. No generic checklists.
Keep / Fix / Defer memo
What's working, what matters now, and what you can safely ignore this quarter.
Sequenced action plan
The next moves in order, sized so you (or your AI) can execute them.
Live walkthrough
We go through it together. Bring your questions and your co-founder.
NOT IN THE BOX Implementation, penetration testing, compliance certification, emergency response, and unlimited support. The audit gives you clarity. It doesn't make me your on-call.
How I think
Keep what works. Fix what matters. Defer the rest.
Anyone can hand you a list of problems. The judgment is in what you deliberately leave alone. Here's the shape of a real memo.
Case file: illustrative
B2B SaaS. Built in four months
with an AI app builder, Postgres, and
Stripe. 40 paying teams. Solo founder.
The decision: "Do we rewrite
before I hire my first engineer?"
KEEP it's working
Postgres
It will carry you well past your next 10×. The tool isn't the problem.
The monolith
One deployable is a feature at 40 customers. Microservices now would be a rewrite in disguise.
The AI-built UI
Customers like it. Ugly code that nobody complains about is not this quarter's risk.
FIX this month
Tenant isolation on 3 tables
One team can read another team's invoices through the API. Fix this week.
Stripe webhooks without idempotency
A retried webhook can provision a seat twice. Small fix, expensive bug.
A restore nobody has tested
Backups exist. Whether they work is a guess. Test one restore before you need it.
DEFER on purpose
The full rewrite
Buys nothing your customers or your next hire need this quarter.
Kubernetes
You don't have that problem. You may never have it.
100% test coverage
Cover the money path and the auth path. The rest can wait.
RECOMMENDATION
Don't rewrite. Fix three things in two weeks, then hire a product engineer, not a platform engineer.
A composite example, not a client. Real memos cite files, queries, and evidence.
Who's reading your code
I still write code for 64 kilobytes.
I'm Abed Lawand, a working CTO and software architect. I build cloud systems for a living, and in my spare time I write 6502 assembly for a 40-year-old computer with 64KB of RAM. It still teaches me things no framework ever has.
Constraints reveal architecture. When nothing is hidden, you can finally see what you own.
That's the lens I bring to your product. No framework religion, no rewrite agenda. Just what's actually there, and what it means for the decision you're about to make.
64KBRAM, still enough
6502Assembly, real hardware
1Audit at a time
The book
The Vibe Coder's Guide to Software Architecture
The questions to ask about the software you built with AI, for founders and solo builders who shipped first and want to understand second. The audit applies those questions to your product.
Get updates in the newsletter →
The newsletter
Clarity before complexity.
Practical notes on architecture, engineering judgment, and building systems that last. Written for people who ship.
✓ You're in. Clarity incoming.
Couldn't reach the server.
Finish subscribing on Beehiiv →
No noise. Unsubscribe anytime.
Press start
Every week you wait, there's more to understand.
You did the hard part: you shipped. Let's make the next decision a good one, while the system is still small enough to see whole.
One audit at a time. The slot is open.Current slot taken. Join the queue.