2025-11-02 · philosophy · engineering

First principles against folklore

Every estate accumulates folklore. Restart it twice. Don't touch that cron. We always set this sysctl. The ticket that fixed it last time. None of this is stupid. Folklore is compressed incident memory. It is also how a platform becomes a museum.

First principles, as I use the phrase at work, is not Descartes with a lanyard. It is a habit: if I cannot point at the mechanism, I do not get to treat the rule as true.

Three questions

  1. What is the invariant? Not the tool. The invariant. "Keys must exist only in Vault and live for less than N days" is an invariant. "Use this Ansible role" is a tactic.
  2. What fails, and how do we see it? A control without an observation is a wish. Logging that cannot answer "which host drifted from baseline at 02:13" is décor.
  3. Who is the next operator? If the answer is "me, because I remember", the system is unfinished.

These questions are philosophical in the old sense: they are about what we claim to know. Socrates is not a stretch here. Most outages I have worked were not novel physics. They were a story we had agreed not to re-examine.

Ethics is not a slide at the end

I used to write "AI ethicist" on a student website because I had been near models that classify people and scenes, and I did not like the shrug. The shrug has a production form. We ship automation that can take a host out of a trading path, rotate every secret, or deny a build. That is moral work even when the payload is YAML.

A good automation is legible. A bad one is a ritual with a logo. Legibility is how you stay accountable to the people who did not attend the design review — including the ones who will be asleep when it fires.

What I keep from the old games

The FPS agent taught me a cheap lesson that survived contact with a bank: the environment is the curriculum. If your staging is a cartoon of production, you will train a cartoon policy. If your pipeline tests the image the traders actually boot, you will learn the real failure modes.

Philosophy without an environment is a blog. Engineering without philosophy is folklore with better CI.

I would rather be slow on a sentence and fast on a rollback.