Software is opinion, compiled
You can read a company's real values in its constraints faster than in its mission statement — in what it made impossible and what it refused to hardcode. Those choices are beliefs compiled into behavior: the database schema is a worldview, the permission model is a theory of trust, and whatever you automated is what you decided was beneath a person's attention. Every default is an argument you have stopped having — so you had better be right about it.
You can read a company's real values in its codebase faster than in its mission statement. Not in the comments — in the constraints. What did they make impossible? What did they refuse to hardcode? Those choices are beliefs, compiled into behavior.
When I set the rule that no client name may ever be hardcoded, I was not making a technical decision. I was declaring that the system belongs to everyone who will ever use it, not to whoever we onboarded first. Every architecture encodes a theory of who matters.
Show me what you refused to hardcode and I will show you what you believe.From the essay
This is the quiet ethics of building. The database schema is a worldview. The permission model is a theory of trust. The thing you automated is the thing you decided was beneath a person's attention — and you had better be right about that.