Engineering Management

Story points, t-shirt sizes, and ideal days all try to predict how long work will take by guessing harder. The data your team already has predicts better than any guess — if you stop estimating and start counting.

Flaky CI doesn't just slow you down. It teaches engineers to ignore red. Once that habit forms, your test suite stops being a safety net.

Scripts nobody maintains, CLIs with no docs, dashboards with no owners. Internal tooling kills DevEx silently — because it's nobody's job to fix it.

Most teams treat local setup as an afterthought. Cold start time over 10 minutes is a retention killer for new hires and a daily tax on everyone else.

Day-to-first-PR, day-to-first-deploy, day-to-unblocked. Teams that measure onboarding speed ship faster. Most teams measure nothing.

AI made engineers 10x faster. PMs didn't keep up. Andrew Ng named it. LinkedIn already restructured around it. Here's what your team should actually do.

AI just cut engineering cycle time by 80%. Your feature-decision process still takes three weeks. You didn't solve delivery. You exposed discovery.

AI agents can execute from a precise spec. The real bottleneck shifted from writing code to writing what you want — clearly. Here's what changed, why it matters for engineers, PMs, and managers, and how to actually do it.

The org chart most teams run was designed when humans wrote all the code. Anthropic's 2026 data says that assumption is gone. Here is what the structure should look like now — and what roles actually matter.

Faros AI tracked 22,000 developers and found individual AI gains evaporate at the org level. PR merge times are down 20%. Incidents are up 23.5%. Here is the mechanism — and what actually fixes it.

PR turnaround time is the most undervalued engineering metric. Here's how to cut it from days to hours without sacrificing quality.

A playbook is only useful if a stressed engineer can follow it half-asleep. Here's the structure that survives real incidents.

Microservices are an organizational solution to a coordination problem you don't have yet. Here's when they actually help — and when they're a foot-gun.

On-call is a tax on your team. Done badly, it's the reason senior engineers quit. Here's the rotation design that actually works.

Every 100 lines of diff doubles the time to merge. Here's why, and what to do about it.

Story points don't predict delivery. Velocity charts don't measure velocity. Here's how to plan engineering work without the agile cosplay.

It's not the meetings. It's what the meetings mean. The fix isn't fewer meetings—it's meetings with actual stakes.

Your engineers are customers. Your product is their velocity and happiness. You're not managing engineers—you're shipping team output.

Rewrites sound good in theory. In practice, 75% fail. Here is how to tell if yours is the 25%.

Hiring managers ask about sorting algorithms. Good engineers ask about your incident response. Here is what actually predicts job performance.

The team that shipped in 6 months takes 18 months for the next feature. Growth killed the thing that made them great. Here is why it happens and how to prevent it.

Every missed deadline traces back to decisions made years ago. A CFO's guide to understanding why your code is expensive and how to budget for it.

Every team quietly raising the bar on junior reqs thinks it's being smart. They're building a talent debt that won't show up on any dashboard until it's already too late.