Documentation Drift: When the Map Stops Matching the System
Documentation stays trustworthy when it is owned, tested against reality, and updated through the same workflow as the system.
From the journal
Latest articles
Practical perspectives on infrastructure, software delivery, and the systems connecting them.
Service Ownership: Every System Needs a Named Steward
Named service stewardship connects technical health, business purpose, documentation, incidents, and lifecycle decisions.
Decommissioning Infrastructure Without Leaving Ghost Assets
Complete decommissioning removes equipment, access, data, monitoring, billing, dependencies, and obsolete records together.
Refactoring Production Systems Without Stopping Delivery
Production refactoring works best as a sequence of observable, reversible changes tied to product delivery.
Maintenance Windows as a Designed Operational Product
A good maintenance window has a clear customer promise, tested procedure, decision authority, telemetry, and recovery path.
Schema Evolution Without Permanent Compatibility Layers
Safe schema evolution separates expansion, migration, validation, and cleanup so temporary compatibility code stays temporary.
Lifecycle Planning for Switches, UPS Units, and Access Points
Infrastructure replacement should follow condition, support, capacity, and risk instead of waiting for hardware failure.
Technical Debt with an Expiration Date
Technical debt becomes manageable when teams record its purpose, cost, owner, review date, and exit condition.
Infrastructure Labels That Survive Staff Turnover
Durable labels connect physical equipment to a maintained source of truth without depending on tribal knowledge.