Design / 012
Open / Closed Principle
Designing for extension without reopening stable code.
Software engineering, architecture, systems, code, and production lessons — a long-running record of what survived contact with reality.
Only one reason to change.
Designing for extension without reopening stable code.
Indexes, plans, statistics, and query behavior observed under production load.
Command-line operations, scripts, migrations, and infrastructure lessons preserved in context.
Tradeoffs that only become visible after software meets scale and time.