Lessons Learned

A lesson is only real when it changes behaviour. These did — each one is now built into a template, a check, or a habit.

Engineering

• Silent failure is the enemy, not failure. Anything that runs unattended must be able to announce its own breakage. Green that cannot go red is not green; it is unknown.
• Boring technology is cheaper over its whole life. The clever tool costs you later, when you have forgotten how it works.

Editorial

• Length is not depth. A 450-word piece dressed as an essay serves no one. Say the whole thing, or say it briefly and honestly — but do not inflate.
• A claim without a source is an opinion. If an essay asserts a fact, the reference must be real. One fabricated citation costs more trust than a hundred real ones earn.

Product

• Ship the smallest honest version. A read-only tool that works beats a full tool that might. Trust is built in increments, and so is software.
• The default answer to “should we add this?” is no. Every feature is a permanent liability. Subtraction is underrated.

Knowledge

• Knowledge that does not change behaviour is just storage. The point of writing a lesson down is that the next decision inherits it automatically.
• Freshness is a property, not an afterthought. A confident answer built on a stale note is worse than no answer.

AI

• AI proposes; humans dispose. The value is in diversity of attention, not autonomy. Keep the gate.
• Constrain the model, then let it run. A strict prompt (“only real sources, or none”) plus a human check produces better work than an unconstrained model left to publish.

Operations

• Version everything; then you can be brave. With a clean history and instant revert, aggressive change becomes safe change.
• Automate the compliance check, never assume it. “We’ll add that later” is how three bots end up existing on paper but never running.

The through-line across every domain is the same: build the correction into the system, not into someone’s memory. Memory fades. A default does not.