Fiber Path Documentation as Source of Truth
Fiber documentation should describe more than endpoints. It should preserve route, conduit, strand, patch, ownership, and failure-domain context.
From the journal
Latest articles
Practical perspectives on infrastructure, software delivery, and the systems connecting them.
Telemetry Contracts: Designing Events That Survive Scale
Telemetry events become production interfaces. Treat their names, fields, cardinality, and privacy rules like contracts.
Capacity Planning for PoE, Cooling, and Edge Compute
Capacity planning has to connect power, heat, ports, and compute. A rack can be full long before it runs out of space.
Cost-Aware Rendering: Making Frontends Budget Themselves
Rendering choices have a cost profile. Frontends should understand when to spend CPU, network, cache, and edge compute.
Sensor Fusion for Smart Server Rooms
A smart server room is not a room with more sensors. It is a room where temperature, power, airflow, acoustic, and network signals explain each other.
The Trust Audit: CodeVelo's July Automation Checklist
Automation should be fast, observable, bounded, and reversible. This July checklist reviews trust from the wiring closet to the deployment pipeline.
Rollback-First Architecture
A rollback-first architecture treats recovery as a design requirement, not a hopeful button added after deployment.
Edge AI Gateways in the Wiring Closet
Edge AI gateways bring inference close to cameras, sensors, and access systems, but the wiring closet needs power, cooling, security, and lifecycle planning.
Data Contracts for AI-Generated Features
AI-generated output needs contracts just like API responses do. Validate shape, source, confidence, and allowed use before the feature reaches users.