Charity Majors (Honeycomb): "Developer cycles are the scarcest resource in your company, and you want to spend as many of those as possible on your core product." The framing reorders the classic resource conversation: money, servers, and time are secondary to focused engineering attention. Every cycle spent on infrastructure, on-call, or tooling is a cycle not spent on differentiated product. This is the ROI case for platform engineering: not cost reduction, but attention recovery. A platform team that eliminates 2 hours/week of infra friction per engineer across 50 engineers recovers 100 developer-hours/week — without hiring. ## Cross-Domain Applications **Startup prioritization**: Feature roadmap decisions should be filtered through "does this compound the team's ability to focus on core value?" — outsourcing non-core functions applies the same principle. **Personal productivity**: Deep work (Cal Newport) frames attention as the scarcest resource for knowledge workers — same logic, individual scale. **Parenting / caregiving**: Caregiver attention (not time) is the scarcest resource; tasks that drain attention (even if brief) are higher-cost than they appear. **Business strategy**: Warren Buffett's "circle of competence" — allocate attention to where you have asymmetric advantage; outsource the rest. ## Related Concepts - [[Amplified Intelligence]] — Human attention/cycles as critical input bottleneck in AI systems (quality in = quality out) - [[Thinnest Viable Platform]] — Minimal platform surface to maximize developer focus - [[Cognitive Load Cost of You Build It You Run It]] — Tradeoff between ownership and distraction - [[Golden Path as Opinionated Enablement]] — Intentional constraints to preserve attention ## References - [[Platform Engineering, DevOps, and Cognitive Load]] (InfoQ, Oct 2022) - Charity Majors, CTO Honeycomb