Writing
Write-ups about infrastructure, software architecture, and what I learn while building.
Kubernetes → Prometheus → Cortex → Grafana / Logs → Loki / Traces → OpenTelemetry → Tempo
A stack is only useful when it helps you ask sharper questions during stress. Metrics explain shape, logs explain texture, traces explain path.
TAKEAWAYI prefer systems where each tool has a clear boundary and the architecture can be reasoned about under stress.
Runbooks as tools, incident tickets as memory, deterministic exploration maps, and MCP servers as controlled action layers.
TAKEAWAYGood agents do not replace judgment. They compress the distance between question, evidence, and reversible action.
Frontend, backend, database, auth, deployment, observability, and product thinking are not separate rooms. They are pressure points in the same machine.