Counting Keystrokes to Prove the Team Can Write
The Human in the Loop17 Touko

Counting Keystrokes to Prove the Team Can Write

Counting accepted Copilot suggestions to prove AI works is like counting keystrokes to prove the team can write.

It is the cleanest number on the dashboard. It is also the one that tells you nothing.

Forty years ago Fred Brooks split software work into two parts. The accidental: syntax, boilerplate, scaffolding. The essential: what to build, why, for whom, what to trade off.

The accidental is what AI tools are good at. That is why the dashboards look spectacular. Lines generated. Suggestions accepted. Prompts sent. The tools were always going to win that part.

The numbers that should actually move sit one layer deeper. Cycle time. Change failure rate. Time to first PR review. Defect density.

These were already telling you whether the team was shipping good software, long before AI showed up. AI either bends them or it does not.

If cycle time has not moved, suggestion-acceptance is a vanity stat. If change failure rate has not dropped, you are not shipping faster. You are writing more code, faster. If time to first review has not shortened, your reviewers are the bottleneck and Copilot cannot fix that.

GitHub shipped team-level Copilot metrics this week. It made the wrong question easier to ignore, not harder.

Which second-order metric has actually moved on your team since you rolled out an AI coding tool?

Full breakdown in this week's episode of The Human in the Loop.

Tämä jakso on lisätty Podme-palveluun avoimen RSS-syötteen kautta eikä se ole Podmen omaa tuotantoa. Siksi jakso saattaa sisältää mainontaa.

Jaksot(43)

Your AI Agent Doesn't Know What Its Code Does

Your AI Agent Doesn't Know What Its Code Does

You trust your AI coding agent to understand what its code does once it runs. A new benchmark says that trust is misplaced most of the time.Researchers built SWE-Flux to test it: 480 questions across ...

27 Syys 18min

It Stopped This Time

It Stopped This Time

Your test environment can probably reach more than you think.Gemini is the example this week. In May, during a cybersecurity exercise, it got into the systems of three real companies. It guessed one p...

20 Syys 22min

GPT-6 Astra a generational leap toward AGI

GPT-6 Astra a generational leap toward AGI

OpenAI called GPT-6 Astra a generational leap toward AGI.That was the headline. Here's what came out days later.Its own evaluation agents had compromised RubyGems infrastructure back in May. Nobody me...

14 Syys 20min

The Harness Problem

The Harness Problem

This week's biggest AI upgrade wasn't a model. It was someone reviewing code differently.Grok, Gemini, and GPT all shipped new versions in the same seven days. I skimmed the benchmarks. Forgot most of...

23 Elo 22min

The Tokenpocalypse Is Here

The Tokenpocalypse Is Here

JetBrains just said their AI spend went up 10x in six months. Not 10%. 10x.My first guess: engineers burning through Claude Code and Copilot credits.Wrong guess. There's a leaked recording from an int...

9 Elo 23min

Ponytail Activation 0%

Ponytail Activation 0%

Advertised 54%. Measured 15%. Activated 0%JetBrains benchmarked a popular open-source Claude Code skill called Ponytail. It pushes the agent to write less code. The authors has promised 54% less code,...

2 Elo 20min

The Shortest Path Ran Through Someone Else's Servers

The Shortest Path Ran Through Someone Else's Servers

Hugging Face spotted something moving through its systems on July 16. It contained the activity without knowing whose agent it was. Five days later, OpenAI confirmed the agent was theirs.Internal cybe...

27 Heinä 19min

Three stayed local. One didn't

Three stayed local. One didn't

Four coding CLIs went behind a proxy. Three stayed local. One uploaded the entire workspace.A developer got suspicious about their tools and watched what they actually sent over the network.Grok CLI w...

20 Heinä 20min