AI Doesn't Make Your Team Faster. Shared Infrastructure Does.
Individual AI speedups are a distraction. The real gains come from treating AI as team infrastructure -- embedded in docs, decisions, and onboarding.
Productivity
Definition
Productivity coverage in this archive spans 12 posts from Aug 2019 to Mar 2026 and treats productivity as a production discipline: evaluation loops, tool boundaries, escalation paths, and cost control. The strongest adjacent threads are ai, developer tools, and leadership. Recurring title motifs include developer, ai, experience, and management.
Working claims
- The archive repeatedly argues that productivity only creates leverage when it is wired into an existing workflow.
- Early posts lean on developer and metrics, while newer posts lean on ai and tracked as constraints shifted.
- This topic repeatedly intersects with ai, developer tools, and leadership, so design choices here rarely stand alone.
How to apply this
- Define quality gates up front: eval sets, guardrails, and explicit rollback criteria.
- Start with the newest post to calibrate current constraints, then backtrack to older entries for first principles.
- When boundary questions appear, cross-read ai and developer tools before committing implementation details.
Where teams get burned
- Shipping agent behavior without hard boundaries for tools, data access, and approvals.
- Optimizing for model novelty while ignoring reliability, latency, or cost drift.
- Applying guidance from 2019 to 2026 without revisiting assumptions as context changed.
Suggested reading path
- Start here (current state): The Throughput Engineer: Why Headcount Is a Lagging Metric
- Then read (operating middle): My Honest Take on GitHub Copilot After Six Months
- Finish with (foundational context): Internal Platforms vs. Ad-Hoc Tooling: Which Developer Experience Actually Wins
Related posts
- The Throughput Engineer: Why Headcount Is a Lagging Metric
- AI Developer Experience: Current State
- AI-Powered Knowledge Management
- AI Doesn’t Make Your Team Faster. Shared Infrastructure Does.
- AI Pair Programming: It’s a Junior Dev, Not a Wizard
- I Tracked My AI-Assisted Coding for Three Months. Here Are the Numbers.
- My Honest Take on GitHub Copilot After Six Months
- Engineering Metrics That Actually Matter
References
AI Pair Programming: It's a Junior Dev, Not a Wizard
AI coding assistants are useful when you treat them like a fast, literal junior teammate. Give them constraints, review their output, and stop expecting architectural insight.
I Tracked My AI-Assisted Coding for Three Months. Here Are the Numbers.
After three months of tracking Copilot and GPT-4 usage across real projects, the productivity picture is messier than the marketing suggests.
My Honest Take on GitHub Copilot After Six Months
Six months with Copilot in real projects. What it actually helps with, where it quietly makes things worse, and why the productivity claims are overblown.
Engineering Metrics That Actually Matter
Most engineering metrics measure activity, not outcomes. Here is how to pick the few that actually improve delivery and reliability.
GitHub Copilot: First Impressions From a Go Developer
I got early access to GitHub Copilot's technical preview. Here's what it actually does well, what it gets wrong, and why I'm cautiously interested.
Embracing Remote Work: Benefits, Dangers, and Overcoming Challenges
After years of building and running distributed engineering teams, here are the actual benefits, real dangers, and hard-won lessons about making remote work stick.
Most Developer Productivity Metrics Are Management Theater
Lines of code, velocity charts, commit counts — most developer productivity metrics are garbage. DORA metrics are the only ones worth your time.
Internal Platforms vs. Ad-Hoc Tooling: Which Developer Experience Actually Wins
A comparison of two approaches to developer experience -- purpose-built internal platforms versus the organic tooling that teams build for themselves -- and when each one actually delivers.