The Sacred Files Registry
Every team has a list of files nobody is supposed to touch. The structural version is that the build won't let them.
Rise of the Agent Org · 8 minute read · By Ed | Founder & CEO, DealiOS
A team at a normal company decides to clean up the authentication code. The code is messy. It's been there for three years. Refactoring it has been on the engineering backlog for a year. Two senior engineers pair on it for a day. The pull request looks good. The reviewer approves. The tests pass. It ships on Tuesday afternoon.
On Wednesday, customers start seeing other customers' data.
Nobody did anything wrong, exactly. The engineers were skilled. The reviewer was competent. The tests were the tests. The change passed every gate the team had. The gate the team didn't have was the one that said: this specific file does not get refactored, ever, by anyone, period, regardless of how skilled they are or how good the PR looks.
Continue reading.
Enter your email to unlock the full paper. And the rest of the Architecture Library.