Why The Last 10% Takes 90% of the Time

Your app works. But does it actually work?

Remaining Features
0
Remaining Time
0

This is the developer's nightmare. And AI just made it worse.

•••

What Even Is The Last 10%?

The stuff that's 80% invisible to users but 100% visible when broken.

Edge Cases User enters emoji in phone field. User uploads 50GB file. User's name is O'Brien.
Error States What happens when API fails? When network drops? When server returns 500?
Loading States Spinners, skeleton screens, progress indicators. The in-between moments.
Accessibility Keyboard navigation. Screen readers. Focus management. ARIA labels.
Polish Animations that don't jank. Micro-interactions. Visual feedback. Delight.
Cross-Browser Compatibility Safari being Safari. IE11 ghosts. Mobile viewport quirks.

None of this shows up in your demo.

•••

The AI Paradox: Vibe Coding Makes This Worse

Claude writes your MVP in 20 minutes.

You feel like a god.

Then reality hits.

The AI doesn't know your edge casesRare but real user inputs that break your happy-path logic. It writes happy-path code.

You ask it to add error handling — it breaks 3 other things.

Now you're debugging AI-generated code you don't fully understand.

The first 90% felt effortless. The last 10% is quicksand.

20 min MVP Edge case web
•••
Todo App Working prototype 2 hours + Offline mode, sync conflicts 3 days Auth System Basic login 30 min + OAuth, password reset, email, rate limiting 2 weeks

Real Project Timelines

Let's stop pretending.

Here's what actually happens when you build real features:

Todo App

2 hours → working prototype. 3 days → handling offline mode + sync conflicts.

Auth System

30 mins → basic login. 2 weeks → OAuth, password reset, email verification, rate limiting.

File Upload

1 hour → basic upload. 1 week → progress bars, resume on disconnect, file type validation, virus scanning.

Notice a pattern?

•••

Why Claude Amplifies This

The faster you start, the slower you finish.

AI generates code fast You feel productive Skip understanding details Technical debt accumulates Edge case appears Don't know where to fix it Ask AI to fix → Refactors half your codebase

Vibe coding front-loads the dopamine, back-loads the pain.

•••

How to Escape

The goal isn't to avoid the last 10%. It's to not be surprised by it.

Budget Upfront

Assume 3x your initial estimate. If you think it'll take 1 week, budget 3.

Test Edges Early

Ask "what breaks this?" before writing line 100. Not after line 1000.

AI for Scaffolding

Generate the boilerplate. Write the business logic yourself.

•••

Spot The Last 10%

Which feature is actually the hard part?

Question 1: Authentication

Which one takes longer?

Question 2: Data Display

Which one takes longer?

Question 3: Form Handling

Which one takes longer?

If you got all three right, you've been burned before.

•••

The Real Rule

The last 10% isn't actually last.

It's the difference between a demo and a product.

AI makes demos effortless.

Products still require the same hard thinking they always did.

The ratio hasn't changed.

Only your expectations have.

Your move: Budget for reality, not vibes.
Made with scrolly.to by Jerry SoerReport