A client's engineering team adopted AI coding tools across the board. Individual velocity soared. But their DORA metrics flatlined — and the reasons had nothing to do with the tools themselves.
- Published On
productivity
- Last quarter I tracked my time across three consulting engagements. I spent 11 hours a week reviewing AI-generated code and under 8 writing my own. The ratio surprised me, and it changed how I think about developer productivity.
- Published On
- A client's team tripled their PR output with coding agents. Six weeks later, their cycle time had doubled and nobody could explain why.
- Published On
- A consulting engagement where we measured where engineering hours actually went — and discovered the biggest productivity killer wasn't what anyone expected.
- Published On
Tags
consulting (67)debugging (28)architecture (25)developer-experience (22)reliability (19)devops (14)ai (11)performance (9)observability (8)code-quality (7)security (5)technical-debt (5)database (5)microservices (4)testing (4)productivity (4)kubernetes (4)postgres (4)ci-cd (3)databases (3)postgresql (3)infrastructure (3)tooling (3)engineering-culture (3)configuration (2)resilience (2)cost-optimization (2)dependencies (2)nodejs (2)code-review (2)deployment (2)opentelemetry (2)monitoring (2)javascript (2)goals (2)websockets (1)project-management (1)mcp (1)finops (1)multi-tenant (1)authorization (1)terraform (1)dns (1)opinion (1)api-design (1)memory (1)error-handling (1)secrets-management (1)webhooks (1)containers (1)environments (1)queues (1)cloud (1)orm (1)refactoring (1)on-call (1)alerting (1)incident-management (1)typescript (1)distributed-systems (1)caching (1)platform-engineering (1)feature-flags (1)api (1)contracts (1)logging (1)mongodb (1)migration (1)workflow (1)nestjs (1)angular (1)sandbox (1)sonarcube (1)learning (1)journey (1)mdx (1)