Rare knowledge doesn't feel rare
Nobody can hand you a list of what only they know. Knowledge transfer before an engineer leaves starts in your own systems: they already record who to ask.
Latest
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.
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.
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.
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 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.
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.
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 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.
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.
The irreversible decisions go first
Most risks are prices you can pay. The one with no affordable way back is different. Settle those decisions first, while you still have a choice.
Automate what your attention can't change
The work you watch out of habit should run without you. Automation's job: make that true and hand back the attention the watching was quietly costing.
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
Engineering Culture
Reasoning the team can't rerun leaves with the engineer
Team capability transfer holds only when the team can rerun the reasoning themselves. What lives only in the engineer's head leaves with them.
Scaling
The business model is the ceiling
When the business model is the constraint, execution discipline raises the ceiling without breaking it. A diagnostic for model constraints.
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.
Infrastructure
Faster reconciliation doesn't fix drift
Configuration management asks what each value should be. Governance asks whether anyone decided. Drift accumulates in the gap between the two.
Automation
Validation separates self-healing from a keep-alive script
Keep-alive automation checks whether the script ran. Self-healing checks whether the system recovered.
Infrastructure
Procedural risk shrinks; structural risk doesn't
Some risks shrink with effort. Others absorb the same investment and don't move. One question tells them apart during evaluation.
DevOps
Budget constraints are architecture inputs
A spending ceiling changes which tools get selected, where capabilities live, and what never enters the stack.
Team Transformation
Cultural transformation has an error budget
Each practice is a component cutover. The team's own metrics are the SLIs. Regressions consume error budget. Culture shifts as a downstream consequence.
Reliability
Treat your own future memory as unreliable infrastructure
Memory degrades, doesn't transfer, doesn't scale. Self-describing systems survive when the builder forgets, leaves, or gets outnumbered.
Cost Optimization
Application savings are locked behind infrastructure credibility
The largest cloud cost savings live in application code owned by other teams. Reaching them requires trust built through infrastructure wins.