The bug is never where you're looking. It's at the boundary.
GENERAL ARRANGEMENT · THE WHOLE SET
General notes
- 01A boundary is any line where data changes hands: a request enters a server, a document enters a parser, a prompt leaves for a model.
- 02Seven years of production systems. Every serious bug sat on one of those lines. None sat in the middle of a tested function.
- 03One sheet per lesson. Security, AI, engineering, product. All from systems carrying real users and real money.
As posted
The worst bug I ever found was not inside the code. It was on the line between two pieces of code that both worked.
A rider's app reported a distance, and the server believed it. Two requests read one wallet balance in the same second, and both were allowed to spend it. A PDF can carry characters no human can see, and a model will read them anyway.
Seven years of shipping production systems, and the pattern never changes. The middle of the code is fine. The trouble lives at the boundary, where data changes hands and a claim gets treated like a fact.
So this is a set of drawings. One sheet per lesson, drawn the way architects draw buildings: a title block, a revision, a status, and notes you can act on. Security, AI, engineering, product. All of it from systems that carry real users and real money.
Sheet 001 is the general arrangement. The rest follow daily for thirty days.