Infrastructure
An accepted cost is a decision nobody is making
A number that never moves reads as normal in every review it passes through. Reopening one starts with a question about who went looking for the cause.
Infrastructure
Engineering Culture
More architecture won't move the objection
Technical objections survive better architecture when a stakeholder measures a new system with a requirement learned somewhere else.
Infrastructure
A data migration is scoped by what the system can't do yet
A migration estimate prices the copy. Three capabilities the system had before the plan existed decide the rest, and whatever it lacks is the project.
Infrastructure
Your safe migration window closes before the deadline
Migration safety spends time: rehearsal, phased rollout, observation, rollback. Once the schedule can't afford them, the safe migration window has closed.
Architecture
Architecture bends around what you won't change
Designing around components you can't control means picking which side holds the workaround. The one you refuse to change shapes everything else.
Cost Optimization
Cloud cost optimization is an influence problem
Cloud cost optimization becomes an influence problem past the configuration layer, where the savings live in code another team owns and answers for.
Architecture
A constraint you can fail overrules your architecture
An architecture can clear every performance spec and still fail a line that has nothing to do with speed: a price ceiling, a margin it quietly destroys.
Infrastructure
Infrastructure facts don't belong in service code
A fact about infrastructure stored in service code is a second source of truth, and two copies drift. Generate the view from the source instead.
Infrastructure
Migrate one variable at a time, or you won't know what broke
Hold every variable but one and a failure has one suspect. Bundle two and the suspects grow like the subsets: three places to look, then seven.
Infrastructure
A green dashboard is a claim about components
A green board means the components are up. Whether a user can finish the task is a question the system was never built to answer about itself.
Technical Debt
When the constraint moves, reprice the code
Technical debt is extra future cost accepted for a present capability. When the constraint moves, sunk cost keeps the code alive past its expiry
Infrastructure
Redundancy ends where the dependency tree converges
Two backups, two providers, two regions. None of it is redundancy if components share a dependency anyone forgot to map. The failure proves which.