iiinova — where your digital self keeps evolving

Steph Johnson @bkstephj1.bsky.social · 29/07/2026

That moment when a user gets it never gets old. Walked someone through our live demo today. The CLI wizard had everything set up in under a minute. They came in skeptical, but by the time the first issue surfaced automatically, they just watched the agent work.

000

Steph Johnson @bkstephj1.bsky.social · 15/07/2026

Team efficiency is a different goal than individual velocity. The developers I find most interesting right now don’t ask 'how do I ship more with AI?', instead they ask 'how do I make sure what we ship is worth keeping?'

121

Steph Johnson @bkstephj1.bsky.social · 09/07/2026

I could tell you the debugging agent catches and fixes bugs on its own. Or you could just watch it happen.👇 Those of you who know me will appreciate that I set this up myself. VS Code, npm install, the whole thing. The wizard did most of the heavy lifting, which is exactly the point. 😆

000

Steph Johnson @bkstephj1.bsky.social · 24/06/2026

David Fowler nails something that gets glossed over in most AI productivity discussions: 👇 Everyone is celebrating the speed of shipping. Fewer people are asking what happens to the codebase six months later when nobody fully understood what they shipped.

100

Steph Johnson @bkstephj1.bsky.social · 27/05/2026

Give your coding agent the data it needs to automatically fix bugs. APMs sample heavily and miss critical content. Multiplayer captures unsampled, full-stack session data and feeds your agent exactly the runtime context it needs. Confident fixes start with complete runtime data.

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.

110

Steph Johnson @bkstephj1.bsky.social · 16/03/2026

The 10x engineer has never been the person who coded the fastest. This is now more true than ever. And, it should reframe how you think about AI productivity.

100

Steph Johnson @bkstephj1.bsky.social · 06/03/2026

The problem: AI generates code faster than teams can review (and debug) it. The constraint: AI tools need complete visibility into runtime context, not sampled fragments, to more accurately generate code or assist with debugging. The solution: 👇

100

Steph Johnson @bkstephj1.bsky.social · 03/03/2026

This is how engineering leaders triage production issues: 👇 What this matrix doesn't show: the hidden cost of triaging blind.

100

Steph Johnson @bkstephj1.bsky.social · 26/02/2026

AI tools boost velocity but erode deep system knowledge. Debugging and system understanding are the next challenge. Great article by Stephane Moreau: open.substack.com/pub/blog4ems...

000

Steph Johnson @bkstephj1.bsky.social · 23/02/2026

Teams are rushing to add AI debugging to their observability stacks. But if the underlying data is: • Aggressively sampled • Missing payloads • Scattered across disconnected tools Adding AI on top just means faster access to incomplete data. Fix the data problem first.

000

Steph Johnson @bkstephj1.bsky.social · 19/02/2026

Imagine you're looking for a specific email, but: ‣ Your inbox has 100,000 of them ‣ They're all labeled "Email" ‣ There's no search function ‣ Some emails are in Gmail, some in Outlook, some in Yahoo That's what AI agents face when trying to debug your system. 🧵

100

Steph Johnson @bkstephj1.bsky.social · 17/02/2026

If your observability data isn't correlated across frontend and backend (or you're missing critical data due to sampling or lack of instrumentation) adding AI on top won't fix it. It'll just give you faster access to incomplete information. AI debugging is only as good as the data you feed it.

010

Steph Johnson @bkstephj1.bsky.social · 13/02/2026

The best engineers were never the ones who wrote code fast or with “clever” solutions. The gap between top and bottom performers continues to widen.

100

Steph Johnson @bkstephj1.bsky.social · 28/01/2026

There a debugging bottleneck few talk about: the hours engineers spend reconstructing what happened in production because critical context is missing. For example: • What payload did we send? • What did the external API return? • Which headers were set? • What did the middleware modify?

100

Steph Johnson @bkstephj1.bsky.social · 23/01/2026

Which pie chart is your team living in? This is the difference between 3 hours of context switching and 10 minutes of clarity. Bad debugging = manual correlation across scattered tools. Good debugging = auto-correlated runtime context in one place.

010

Steph Johnson @bkstephj1.bsky.social · 16/01/2026

Not all session replays are built for the same job. 📊 Product analytics tools answer questions about user behavior. 🪲 Debugging tools need to answer questions about system behavior. When bugs span APIs, services, and data layers, engineers need replays that correlate user actions to backend data.👇

010

Steph Johnson @bkstephj1.bsky.social · 12/01/2026

Building developer tools means constantly stress-testing your own assumptions. If you signed up for Multiplayer and bounced during onboarding, understanding why is incredibly valuable to us. We’re offering a $50 gift card for a short conversation about your experience (15–20 min).

100

Steph Johnson @bkstephj1.bsky.social · 30/12/2025

Question for teams using LogRocket: how much time do you spend jumping between tools to connect frontend issues to backend problems?

110

Steph Johnson @bkstephj1.bsky.social · 24/12/2025

1/ Looking back at 2025, what stands out the most isn’t one single thing. It’s how a very small team managed to ship our product and achieve our goal: making debugging faster, less fragmented and less manual. And, they did it without sacrificing their sanity.

100

Steph Johnson @bkstephj1.bsky.social · 19/12/2025

For engineering teams: what percentage of bugs in your app are purely frontend vs. backend or integration issues? As systems become more complex, partial visibility creates friction across support and engineering. This 👇 highlights why end-to-end context is becoming table stakes for debugging.

030

Steph Johnson @bkstephj1.bsky.social · 02/12/2025

Teams design distributed systems and then try to debug them with workflows built for monoliths.👇 That’s why I’m such a believer in session-based visibility: pulling every layer of the system into one full stack session recording so engineers can investigate, debug, and fix issues faster.

020

Steph Johnson @bkstephj1.bsky.social · 28/11/2025

I wish I could laugh, but it’s an uncomfortable truth most executives overlook. We obsess over churn rates and retention metrics, yet rarely measure how much inefficient debugging and support workflows cost the company (and who they actually serve).

030

Steph Johnson @bkstephj1.bsky.social · 25/11/2025

Fullstory is fantastic for understanding user behavior. But debugging technical issues? That usually needs more than a replay of the UI. For engineering teams that need deeper visibility there's Multiplayer. dev.to/rohan_rajpal...

dev.to

Multiplayer vs Fullstory

Session replay tools have become a key component of testing and debugging workflows in recent years....

040

Steph Johnson @bkstephj1.bsky.social · 19/11/2025

Raise your hand if this describes your technical support 👇 👀 If this feels familiar, I’d love to hear what’s working (or not) in your support flow. Ping me in the comments or DMs. My take: the real problem isn’t the bug. It’s the missing context.

010

Steph Johnson @bkstephj1.bsky.social · 11/11/2025

User: What’s the benefit of switching to @multiplayer.app ? Me: 👇

011

Steph Johnson @bkstephj1.bsky.social · 06/11/2025

We tend to talk about innovation as if it comes from sudden sparks of genius: one person, one idea, one breakthrough. But most progress doesn’t look like that. It’s rarely a lightbulb moment. It’s actually more like a relay race. 🧵

100

Steph Johnson @bkstephj1.bsky.social · 03/11/2025

End-user support is supposed to be simple: a user reports a problem, the team fixes it, everyone moves on. In reality, it’s usually a marathon of manual steps, tool-switching, and endless back-and-forth. What’s tricky is that this marathon often ends with a (deceptively) positive outcome: 🧵👇

100

Steph Johnson @bkstephj1.bsky.social · 21/10/2025

Looking for AI-related ice breakers for tomorrow’s MCP demo night in NY. Would this do? 😉

010

Steph Johnson @bkstephj1.bsky.social · 16/10/2025

Guess the team at Anthropic could’ve used a Multiplayer session replay for that one 👀

010

Steph Johnson @bkstephj1.bsky.social · 08/10/2025

Capture a full stack session recording once, use it for debugging, testing, support, feature development, and AI prompts. Here's everything you can do in Multiplayer 👀 👇

100

Steph Johnson @bkstephj1.bsky.social · 01/10/2025

The best way to ‘win’ at Product Hunt is… not to chase upvotes? 🤔

010

Steph Johnson @bkstephj1.bsky.social · 30/09/2025

Product hunt is dead. Here’s what happened as soon as we launched Multiplayer 👇. But here’s also why we did it anyway 🧵

100

Steph Johnson @bkstephj1.bsky.social · 30/09/2025

We didn't launch on one of the biggest Product Hunt launch days of the last few weeks to “win”. We launched to share why full stack session recordings matter.

010

Steph Johnson @bkstephj1.bsky.social · 25/09/2025

Our first post on Hacker News 🤩 This feels like a rite of passage. news.ycombinator.com/item?id=4537...

000

Steph Johnson @bkstephj1.bsky.social · 25/09/2025

Debug faster, validate fixes, and even feed the whole story into your AI IDE. Multiplayer’s full stack session recordings allow you to seamlessly capture and resolve issues or new develop features - without breaking your flow.

020

Steph Johnson @bkstephj1.bsky.social · 11/09/2025

We need to stop treating documentation as a static pile of text. The future is documentation as an experience: dynamic, contextual, and part of the workflow. Otherwise, the vicious cycle of outdated docs will never end.

100

Reposted by Steph Johnson

Tom Johnson @tomjohnson3.bsky.social · 11/09/2025

I had the chance to speak at API World 2025 last week on a topic I’ve seen frustrate teams for years: API documentation. Because let’s face it: most developers don’t want to read static docs. Outdated Postman collections and PDF references slow everyone down.

131

Steph Johnson @bkstephj1.bsky.social · 28/08/2025

When we build something at @multiplayer.app, we aim for insanely great quality. For example: we’ve been building a sandbox so you can test Multiplayer without signing up for a free trial. Seems straightforward, right? But in practice, there’s a lot to think through 👇

111

Steph Johnson @bkstephj1.bsky.social · 19/08/2025

A GTM tip for anyone building for developers: If every feedback call is positive, it means you are only talking to fans and you are not learning enough. Growth comes from talking to people who are struggling with some aspect of your product because its likely they are not the only ones.

000

Steph Johnson @bkstephj1.bsky.social · 15/08/2025

There’s a difference between searching the entire game to review a play and seeing it from the player’s helmet cam. --- That’s the difference between observability tools and Multiplayer.

000

Steph Johnson @bkstephj1.bsky.social · 13/08/2025

Multiplayer doesn’t try to show you everything. It shows everything that matters for a single bug, test run, or user session. It’s not about coverage; it’s about clarity.

010

Steph Johnson @bkstephj1.bsky.social · 08/08/2025

If your AI can write code but can’t help fix bugs, you’re only solving half the problem.

000

Steph Johnson @bkstephj1.bsky.social · 01/08/2025

“Works on my machine” isn’t just a joke. It’s a symptom of broken workflows.

010

Steph Johnson @bkstephj1.bsky.social · 29/07/2025

❝An information retrieval system will tend not to be used whenever it is more painful and troublesome for a customer to have information than for him not to have it.❞ 👇 That’s why we focused on getting devs *all* the data for a bug, in a single timeline.

000

Steph Johnson @bkstephj1.bsky.social · 22/07/2025

If every outage still ends with 'can someone repro this?', you don’t have a reliable test case (👀👇). You have a one-off incident waiting to happen again.

000

Steph Johnson @bkstephj1.bsky.social · 18/07/2025

Every minute your engineers spend reconstructing context is a minute they’re not solving problems.

000

Steph Johnson @bkstephj1.bsky.social · 15/07/2025

You’re debugging a user-reported slowdown in your platform. The logs look fine. Metrics show a latency spike. But you’re stuck. Unsure if the issue is in your database, a flaky third-party API, or somewhere in your internal service calls.

200

Steph Johnson @bkstephj1.bsky.social · 11/07/2025

It’s not “debug once, fix forever.” Unless you’re doing it right, it’s “debug once, waste hours, document never, repeat indefinitely.”

000

Steph Johnson @bkstephj1.bsky.social · 26/06/2025

Traditional observability: investigate the crime scene. Multiplayer: catch the bug in the act, with the receipts. It’s time debugging felt like part of the dev workflow—not an incident report.

031