COOLWHITE

I learned quality in a factory.I run software the same way.

Seven years in consumer-electronics manufacturing for the world's leading brands, five of them on circuit-board assembly lines (PCBA, SMT). The tools changed. The discipline did not.

Why every station counts

Ten stations at 99% each ship only 90% good units.

0.9910 = 0.904 Quality is built in at each station. It cannot be inspected in at the end.

The line

Each factory practice has a place in how I ship software.

On the factory floorIn my software projects
  1. Incoming inspectionEvery issue has the same form: what, where, how to see it.
  2. A frozen production planA milestone with a fixed scope. New ideas wait for the next one.
  3. One station, one jobOne pull request, one change.
  4. A test at every stationAutomated checks run on every change.
  5. Andon: anyone stops the lineA red check blocks the merge. Nothing bad moves on.
  6. Outgoing quality auditA reviewer with no context reads the change cold.
  7. First-article inspectionA release goes to a preview first, then to everyone.
  8. FA/CA and 8DEach incident: why it happened, why it got out, and a guard so it cannot come back.
  9. KaizenThe time of each stage is measured every round. The slowest one gets fixed.

The agent side follows Anthropic's AI-native SDLC playbook: plan, design, build, test, deploy, maintain. The quality side comes from the factory.

Critical to quality

Not every change needs the same rigor. What matters is whether a mistake can be taken back.

A

Cannot be taken back

Keys, logins, user data, update paths, releases.

Independent review. A person approves.

B

Normal

Features and everything else in the code.

Its own tests. Merges when checks pass.

C

Easy to take back

Documents, wording, colors and spacing.

Light checks. Fix forward.

Measured on real projects

35 → 15
Open issues, once grouped by root cause. Five groups held 60% of them.
14 min
One whole-release review. It found three problems that no single change review could see.
4.7 min
Median time for a change to pass its checks and merge, over twelve changes.
  1. DescribeFacts and a timeline. No blame.
  2. ContainProtect the user first.
  3. Two root causesWhy it happened. Why it was not caught.
  4. PreventEach fix is a tracked issue with a guard test.

Want your project run this way?

nick@coolwhite.us