Dispatches / a short note
Haskell teaches you a very important principle
Get rid of the untold rules your team writes every day, and cut down the untold rituals went into codebase, while documented nowhere.
https://blog.haskell.org/a-couple-million-lines-of-haskell/
- “Remember to flush the audit log after every transaction.”
- “Always check the feature flag before calling this endpoint.”
- “Make sure to enqueue the notification inside the database transaction, not after it.”
These are the incantations of operational lore. They live in wiki pages, onboarding documents, half-forgotten design reviews, and the memories of senior engineers who are now three teams away and booked solid until Thursday.
In a company that is hiring aggressively, the half-life of tribal knowledge is alarmingly short. When an engineer leaves, the incantations fade. When a deadline approaches, they are the first thing skipped. When a new engineer joins, they often have no way to know the incantation exists at all. Nothing says “robust system design” quite like a critical invariant living in a Slack thread from nine months ago.