The last ten percent

Most software is finished twice. The first time is when it works on the machine it was built on. The second time is when it works everywhere else, for everyone else, without the person who built it standing nearby.

The gap between those two moments is where projects quietly die.

What the gap actually contains

It is rarely anything glamorous. It is the error message that says what went wrong instead of undefined. It is the form that tells you which field is broken. It is the deploy that does not need a person to remember four steps in the right order.

None of it demos well. All of it is what someone runs into on a Tuesday morning six months later.

Why I care about it

I have handed work over to people who were not developers, and I have watched what happens when something small breaks and nobody knows which thread to pull. The cost is not the bug. The cost is the confidence: once a tool has embarrassed someone in front of their own team, they stop trusting it, and after that they stop using it.

So I would rather spend the extra week on the last ten percent than ship something impressive that quietly becomes someone else's problem.