What Is Technical Debt: A Platform Engineer's Honest Look
For platform engineers, technical debt is not a code quality score. It is a deployment risk that compounds, inflates blast radius, and surfaces in incident post-mortems.
8 articles by Jana Kovacova.
- AI Feature Flags & Progressive Rollouts
- SLO Management & Incident Response
- Platform Engineering & SRE Culture
-
-
What Is Platform Engineering and When Does It Pay Off?
Platform engineering is the discipline of building internal developer platforms. Covers team structure, DORA metrics, golden paths, and whether your IDP investment is actually working.
-
Monorepo vs Polyrepo: What the Blast Radius Tells You
Monorepo or polyrepo: 320 teams benchmarked, the blast radius math, and the 30% rule that high-performing platform teams actually use.
-
Action Items: The Part of Post-Mortems Nobody Gets Right
Post-mortem action items fail not because teams skip the review. They fail because items lack named owners, live in docs nobody reads, and never land in sprint work where engineering actually happens.
-
What Are Feature Flags? A Field Guide for Platform Teams
Feature flags let you ship code to production without exposing it to users. Here is a precise, operational guide to how they work and where the failure modes actually live.
-
AI Assisted Development: Closing the Rollout Safety Gap
Platform teams shipping AI-generated code face failure modes standard error rate and latency gates were not designed to catch. Here is what to instrument instead.
-
8 AI Agent Examples Platform Teams Run in Production
A field guide to AI agent examples that platform teams actually run in production: rollback, triage, diagnostic, and runbook agents, with where each one breaks.
-
Code Refactoring Techniques That Hold in Production
Code refactoring techniques are not about clean code aesthetics. They are about reducing the surface you have to debug at 3am. Here is what actually works in continuous deployment environments.
