1. The idle tells you everything.
Before you rev, before you race, before you even touch the throttle — just listen to it sit there. Does it pulse even? Does it hunt? Does it sound like it forgot what it was doing between cycles?
A codebase at rest does the same thing. If the idle is wrong, the whole build is lying to you.
2. Compression does not negotiate.
Either the cylinder holds pressure or it doesn’t. There is no “mostly sealed.” There is no “good enough for staging.” An engine with low compression in one hole will vibrate itself apart eventually. Code with one weak module does the same. You just cannot feel it from the dashboard yet.
3. Heat is the only truth-teller.
Cold engine runs fine. Cold engine always runs fine. The problem doesn’t show until everything expands, clearances close, and the metal starts touching metal in places it was never supposed to.
Your production system under load is the same. Do not trust the cold bench test.
4. The carburetor hates clean surfaces.
A perfectly clean carburetor will not meter fuel properly. The machined surfaces need a film of fuel residue to wet the air bleeds and transition slots. Too clean and it stumbles every time you open the throttle.
Over-optimized code has the same problem. When you sand off every imperfection, you also sand off the friction that made it work in the real world.
5. The engine does not know your deadline.
You can swear at it. You can throw parts at it. You can stand there with a timing light at 2 AM crying into a beer that has gone warm.
The engine does not care. It will run when the fuel, air, compression, and spark arrive at the same place at the same time. Not before. Not because you asked nicely.
A hard deadline and bad architecture produce the same result. A seized engine and a P1 incident that could have been avoided if someone had just stopped and checked the timing before they hit deploy.
The engine is honest. It is the mechanics who lie to themselves.