I know leaders who live in constant fear that a business-killing bug is lingering in some unread, AI-generated corner of the codebase. Grounding non-deterministic AI output in deterministic input is just one layer of the solution.

Tom Johnson@tomjohnson3.bsky.social · last wk.

I think it’s emotionally exhausting to manage an infinitely hungry AI workforce while knowing there is no longer direct human ownership over every line of code.

I think it’s emotionally exhausting to manage an infinitely hungry AI workforce while knowing there is no longer direct human ownership over every line of code.

Tokenmaxxing was always going to end. Goodhart’s Law doesn’t fail. What replaces it is the more interesting question.

Had a demo call earlier today where the CLI wizard set the live demo up in under a minute. The user's reaction said it all. Very proud of the team for building something that actually works that smoothly. That kind of experience doesn't happen by accident.

Show me a team's review queue and I'll tell you how they're using AI. Reasonable revert rate, reviewers who feel like they're adding value: coding agents being used well.

I recently posted a screenshot of an AI-generated PR with 50k lines of changes. The comments exploded with opinions on PR best practices. Almost nobody stopped to ask whether the review process itself still makes sense. It's like walking past a burning building to debate the exit sign.

Finished doesn't mean closed. One of my favorite things about the Multiplayer web dashboard is that you can reopen any session and keep going in the same thread the agent used the first time.

This is a quote from Cat Wu, Head of Product, Claude Code, 👇 What makes this interesting to me, beyond practical advice, it’s what it signals about the maturity curve of working with AI.

A bloated review queue full of AI-generated PRs isn't a sign that your team is moving fast. Developers who are addressing this problem are taking a step back and thinking about the whole system: what data agents work from, how duplicate issues get caught, what it takes to make a PR worth merging.

If you’re using coding agents, your output numbers (epics completed, task throughput, PR merge rate, …) may look good right now. But those are not the metrics your manager is watching. Every single one of those numbers comes with an asterisk: production quality is declining.

Telemetry built for AI coding agents captures full-fidelity, pre-correlated session data at the source, so an agent isn't reconstructing a failure from sampled traces or scattered tools.

Tom Johnson@tomjohnson3.bsky.social · last mo.

Developers don't want more dashboards to stare at or more alerts to triage. They want the thing that broke, to fix itself. So we don't have to go through this flow of 👇 five tools, eleven steps and four hours just to fix a bug.

Developers don't want more dashboards to stare at or more alerts to triage. They want the thing that broke, to fix itself. So we don't have to go through this flow of 👇 five tools, eleven steps and four hours just to fix a bug.

880+ engineering leaders were asked what challenges their organizations have experienced with AI in the past 6-12 months. 49% flagged security concerns. 48% are dealing with hallucinations. 23% reported an increased need for debugging.

The “10x engineer” was always a simplification and I was very pleased when it started to fade. Then AI coding tools arrived, and it came roaring back. Software engineering is a team sport. The engineers who create the most impact are the ones who multiply the capacity of the people around them.

Yes. Session-based, unsampled runtime data collection is very cool 😎

Today we're open sourcing Multiplayer: run our debugging agent locally, next to your coding agent, and fix production bugs automatically. 👉  github.com/multiplayer-...

GitHub - multiplayer-app/multiplayer: The open-source debugging agent for developers. We connect your favorite coding agent to prod to fix application bugs automatically. Run us locally and eliminate ...

The open-source debugging agent for developers. We connect your favorite coding agent to prod to fix application bugs automatically. Run us locally and eliminate PR slop. - multiplayer-app/multiplayer

github.com

1 in 3 engineering managers is thinking about going back to IC. 37% say their hands-on technical work has increased in the last 12 months. AI made building fast enough to compete with managing again. @leaddev.com latest report puts numbers on what a lot of us have been feeling.

The latest Jellyfish's AI Engineering Trends research shows token consumption climbing sharply, but PR revert rates remain roughly flat across all AI adoption tiers, hovering in the same 0.45%–0.65% band they were in a year ago. More tokens per developer hasn't bought fewer reverted PRs.👇

This meme is a lie and we all know it 👇 Human PR review was always a bottleneck. We merged things we hadn't fully read and shipped things we shouldn't have. The difference now is that coding agents made it worse with PR slop.

First time at #KCDNewYork. Great event, easy to meet people, fantastic food. Met @salaboy.com, newly elected CNCF TOC member and author of Platform Engineering on Kubernetes. Already at the top of my reading pile. See you at the next one. 🙌

Who wants to review this PR? 👇😅 PR reviews were already a known weak point in software development before AI coding agents arrived. They just made it impossible to ignore.

Every major model release makes the same point: the frontier keeps moving. Claude Fable 5 today. Something better in six months. The most underrated decision any engineering team makes right now: building AI workflows that are MODEL-AGNOSTIC.

Anthropic {bot}@anthropicbot.bsky.social · 2mo ago

Introducing Claude Fable 5: a Mythos-class model that we’ve made safe for general use. Its capabilities exceed those of any model we’ve ever made generally available.

I'm speaking at the #DeveloperWeek conference tomorrow in 📍New York. If anyone is interesting in discussing agentic coding, debugging, or just have a coffee, find me and @bkstephj1.bsky.social ☕️

Tom Johnson@tomjohnson3.bsky.social · 2mo ago

Minneapolis last week. New York on June 9-10. I'll be presenting at DeveloperWeek a talk I've been wanting to give for a while: From Alert to Action: Redesigning Your Observability Stack for Agentic AI.

Back in NY from #LDX3 London. 3 sessions in 2 days: AMA panel, a talk on why most MCP servers are collecting dust, and moderating a peer group. The questions after my talk made every hour of prep worth it. @leaddev.com sets the bar high for developer conferences!

It’s hard not to make the connection between between AI output quality and data input. The sooner the distinction between dashboard data and agent data becomes a first-class engineering concern the sooner coding agents will actually deliver on what everyone expects them to do.

“some companies are shipping as many as 50% more defects than before.” This is 👆 from a recent DX report on AI-assisted engineering which confirms what many engineering teams have been quietly noticing: adoption is up, but quality continues to be inconsistent.

I'm speaking at the LDX3 conference next week in 📍London, UK. If anyone is interesting in discussing agentic coding, debugging, or just have a coffee, find me and @vladistevanovic.bsky.social ☕️

Tom Johnson@tomjohnson3.bsky.social · 5mo ago

Built an MCP server recently? Did developers actually use it, or is it collecting dust? 😵 I'll be speaking at @leaddev.com (June 1-2) about why "connecting AI to everything" doesn't work and what actually does when building tools that move from assistants to autonomous agents. See you there? 🇬🇧

“Shift left” has become one of those empty buzzwords that started as genuinely useful and has become misunderstood or misused to the point where it just creates more confusion. See 🧵for the most concrete damage “shift left” does IMO

Replace PR slop with a handful of high-quality PRs. Coding agents prompted by incomplete observability data produce noisy, low-quality PRs that create more review work than they save. Multiplayer provides coding agents unsampled, full-stack session data. Try it for free today: www.multiplayer.app

Debugging Agent for Developers

We connect your favorite coding agent to prod to fix application bugs automatically. Run us locally and eliminate PR slop.

multiplayer.app

Multiplayer@multiplayer.app · 2mo ago

Multiplayer: the debugging agent for developers. We connect your favorite coding agent to prod to fix application bugs automatically. Run us locally and eliminate PR slop.

Minneapolis last week. New York on June 9-10. I'll be presenting at DeveloperWeek a talk I've been wanting to give for a while: From Alert to Action: Redesigning Your Observability Stack for Agentic AI.