Tom Johnson
@tomjohnson3.bsky.social
CTO at Multiplayer.app, full stack session recordings to seamlessly capture and resolve issues or develop new features.
Also: 🤖 robot builder 🏃♂️ runner 🎸 guitar player
Also: 🤖 robot builder 🏃♂️ runner 🎸 guitar player
“Ambiguous screenshots”. It says it all, doesn’t it?
@farisaziz12.bsky.social is describing the nightmare that of debugging vague support tickets, with blurry photos, no reproduction steps, and endless back and forth.
@farisaziz12.bsky.social is describing the nightmare that of debugging vague support tickets, with blurry photos, no reproduction steps, and endless back and forth.
November 17, 2025 at 9:46 AM
“Ambiguous screenshots”. It says it all, doesn’t it?
@farisaziz12.bsky.social is describing the nightmare that of debugging vague support tickets, with blurry photos, no reproduction steps, and endless back and forth.
@farisaziz12.bsky.social is describing the nightmare that of debugging vague support tickets, with blurry photos, no reproduction steps, and endless back and forth.
Does debugging support tickets look like this for you?
If yes, share the latest rabbit hole you fell into.
If yes, share the latest rabbit hole you fell into.
November 11, 2025 at 10:49 AM
Does debugging support tickets look like this for you?
If yes, share the latest rabbit hole you fell into.
If yes, share the latest rabbit hole you fell into.
I’ve spent the better part of the past year working with the OpenTelemetry Collector to ensure our full-stack session recordings include automatically correlated backend traces.
Here are the lessons I’ve learned (sometimes the hard way) about configuring the Collector 👇
Here are the lessons I’ve learned (sometimes the hard way) about configuring the Collector 👇
November 6, 2025 at 4:04 PM
I’ve spent the better part of the past year working with the OpenTelemetry Collector to ensure our full-stack session recordings include automatically correlated backend traces.
Here are the lessons I’ve learned (sometimes the hard way) about configuring the Collector 👇
Here are the lessons I’ve learned (sometimes the hard way) about configuring the Collector 👇
👇 @farisaziz12.bsky.social describes the pain of customer support perfectly.
It’s always exciting to see Multiplayer show up in real-world stories like this, as part of how engineers actually solve problems. Seeing it used to cut through the “screenshot chaos” is exactly why we built it.
It’s always exciting to see Multiplayer show up in real-world stories like this, as part of how engineers actually solve problems. Seeing it used to cut through the “screenshot chaos” is exactly why we built it.
November 3, 2025 at 10:52 AM
👇 @farisaziz12.bsky.social describes the pain of customer support perfectly.
It’s always exciting to see Multiplayer show up in real-world stories like this, as part of how engineers actually solve problems. Seeing it used to cut through the “screenshot chaos” is exactly why we built it.
It’s always exciting to see Multiplayer show up in real-world stories like this, as part of how engineers actually solve problems. Seeing it used to cut through the “screenshot chaos” is exactly why we built it.
"Effective debugging isn’t about speed. It’s about visibility and understanding. When AI has access to complete context, it becomes a real collaborator in that process."
👆 This is exactly why we built Multiplayer. 🤩
👆 This is exactly why we built Multiplayer. 🤩
October 23, 2025 at 7:52 AM
"Effective debugging isn’t about speed. It’s about visibility and understanding. When AI has access to complete context, it becomes a real collaborator in that process."
👆 This is exactly why we built Multiplayer. 🤩
👆 This is exactly why we built Multiplayer. 🤩
Optimizations don’t have to be flashy or complex and a 5-minute fix to our CI/CD pipeline saved us 5hr a day.
This is a reminder that even the most obvious optimizations can hide in plain sight when you’re heads down building the next big thing.
This is a reminder that even the most obvious optimizations can hide in plain sight when you’re heads down building the next big thing.
October 22, 2025 at 8:39 AM
Optimizations don’t have to be flashy or complex and a 5-minute fix to our CI/CD pipeline saved us 5hr a day.
This is a reminder that even the most obvious optimizations can hide in plain sight when you’re heads down building the next big thing.
This is a reminder that even the most obvious optimizations can hide in plain sight when you’re heads down building the next big thing.
A sneak peak of my presentation for tomorrow’s MCP demo night 👀
If you’re in New York - come say hi!
If you’re in New York - come say hi!
October 21, 2025 at 2:27 PM
A sneak peak of my presentation for tomorrow’s MCP demo night 👀
If you’re in New York - come say hi!
If you’re in New York - come say hi!
Claude Code error or human error?
From the latest Anthropic blog post: variable names don’t match (red)…misspelling of urgent (blue) … unnecessary second check (second yellow line)
From the latest Anthropic blog post: variable names don’t match (red)…misspelling of urgent (blue) … unnecessary second check (second yellow line)
October 16, 2025 at 5:26 PM
Claude Code error or human error?
From the latest Anthropic blog post: variable names don’t match (red)…misspelling of urgent (blue) … unnecessary second check (second yellow line)
From the latest Anthropic blog post: variable names don’t match (red)…misspelling of urgent (blue) … unnecessary second check (second yellow line)
Reposted by Tom Johnson
🧵 What is an “AI Engineer,” really?
It’s one of the hottest job titles of 2025 but also one of the most misunderstood. Let’s unpack what the role actually means (and why it matters).
It’s one of the hottest job titles of 2025 but also one of the most misunderstood. Let’s unpack what the role actually means (and why it matters).
October 13, 2025 at 6:01 PM
🧵 What is an “AI Engineer,” really?
It’s one of the hottest job titles of 2025 but also one of the most misunderstood. Let’s unpack what the role actually means (and why it matters).
It’s one of the hottest job titles of 2025 but also one of the most misunderstood. Let’s unpack what the role actually means (and why it matters).
When your AI confidently ‘fixes’ production.
Don’t worry, I’m sure it learned from this. 😅
Don’t worry, I’m sure it learned from this. 😅
October 15, 2025 at 11:52 AM
When your AI confidently ‘fixes’ production.
Don’t worry, I’m sure it learned from this. 😅
Don’t worry, I’m sure it learned from this. 😅
Reposted by Tom Johnson
Sometimes the frontend data isn’t enough.
Sometimes (okay, always) you also want to know what happened in the backend.
Sometimes (okay, always) you also want to know what happened in the backend.
October 7, 2025 at 4:38 PM
Sometimes the frontend data isn’t enough.
Sometimes (okay, always) you also want to know what happened in the backend.
Sometimes (okay, always) you also want to know what happened in the backend.
This is a good time to remind everyone of the AI Darwin Awards. 😆
In a groundbreaking new feature, Tesla FSD introduces "Full Self-Parking" directly on the train tracks.
Read the full story: aidarwinawards.org/nominees/tesla-fsd-train-crossings.html #AIDarwinAwards #HAL9000
Read the full story: aidarwinawards.org/nominees/tesla-fsd-train-crossings.html #AIDarwinAwards #HAL9000
Tesla Full Self-Driving - “Trains vs. Brains” - 2025 AI Darwin Award
Tesla's visionary approach to self-driving technology included the revolutionary concept that railway crossings—with their primitive flashing lights, descending
aidarwinawards.org
October 8, 2025 at 12:15 PM
This is a good time to remind everyone of the AI Darwin Awards. 😆
Devs: I’ll just make a small change.
QA tickets: 🐶🐶🐶🐶🐶🐶🐶🐶
QA tickets: 🐶🐶🐶🐶🐶🐶🐶🐶
October 3, 2025 at 1:56 PM
Devs: I’ll just make a small change.
QA tickets: 🐶🐶🐶🐶🐶🐶🐶🐶
QA tickets: 🐶🐶🐶🐶🐶🐶🐶🐶
MCP servers are everywhere right now. But most are collecting dust.
The key lesson we’ve learned at Multiplayer: scope matters. 🧵
The key lesson we’ve learned at Multiplayer: scope matters. 🧵
What's it like launching an #MCP server into the wild? My latest DirectorPlus edition via @leaddev.com brings in Thomas Johnson, co-founder and CTO of Multiplayer, to discuss helpful lessons learned releasing their MCP server.
leaddev.com/ai/lessons-l...
leaddev.com/ai/lessons-l...
Lessons learned launching an MCP server
Steps you can follow if you're thinking about launching your own MCP server.
leaddev.com
October 1, 2025 at 12:19 PM
MCP servers are everywhere right now. But most are collecting dust.
The key lesson we’ve learned at Multiplayer: scope matters. 🧵
The key lesson we’ve learned at Multiplayer: scope matters. 🧵
I repeat. DON’T UPVOTE. I don’t care about that.
I just want to hear your feedback:
👉 Would you use this mainly for debugging, testing, or feature development?
👉 Have you tried session replays before? What worked, what didn’t?
I just want to hear your feedback:
👉 Would you use this mainly for debugging, testing, or feature development?
👉 Have you tried session replays before? What worked, what didn’t?
Multiplayer is live on Product Hunt 🚀 Here’s how you can support us:
1️⃣ DON’T UPVOTE (yes, you’ve read it right)
2️⃣ COMMENT with your feedback
Upvotes? Nah. Feedback? Yes.
1️⃣ DON’T UPVOTE (yes, you’ve read it right)
2️⃣ COMMENT with your feedback
Upvotes? Nah. Feedback? Yes.
September 30, 2025 at 11:40 AM
I repeat. DON’T UPVOTE. I don’t care about that.
I just want to hear your feedback:
👉 Would you use this mainly for debugging, testing, or feature development?
👉 Have you tried session replays before? What worked, what didn’t?
I just want to hear your feedback:
👉 Would you use this mainly for debugging, testing, or feature development?
👉 Have you tried session replays before? What worked, what didn’t?
I repeat. DON’T UPVOTE. I don’t care about that.
I just want to hear your feedback:
👉 Would you use this mainly for debugging, testing, or feature development?
👉 Have you tried session replays before? What worked, what didn’t?
I just want to hear your feedback:
👉 Would you use this mainly for debugging, testing, or feature development?
👉 Have you tried session replays before? What worked, what didn’t?
Multiplayer is live on Product Hunt 🚀 Here’s how you can support us:
1️⃣ DON’T UPVOTE (yes, you’ve read it right)
2️⃣ COMMENT with your feedback
Upvotes? Nah. Feedback? Yes.
1️⃣ DON’T UPVOTE (yes, you’ve read it right)
2️⃣ COMMENT with your feedback
Upvotes? Nah. Feedback? Yes.
September 30, 2025 at 11:39 AM
I repeat. DON’T UPVOTE. I don’t care about that.
I just want to hear your feedback:
👉 Would you use this mainly for debugging, testing, or feature development?
👉 Have you tried session replays before? What worked, what didn’t?
I just want to hear your feedback:
👉 Would you use this mainly for debugging, testing, or feature development?
👉 Have you tried session replays before? What worked, what didn’t?
Is it ever really possible to get a dev to switch tools once it "works well enough"?
September 29, 2025 at 9:59 AM
Is it ever really possible to get a dev to switch tools once it "works well enough"?
If you haven't yet, I highly recommend checking this collection of reference implementations for the Model Context Protocol (MCP). 👇
September 26, 2025 at 1:31 PM
If you haven't yet, I highly recommend checking this collection of reference implementations for the Model Context Protocol (MCP). 👇
Most “session replay” tools show you what happened in the browser.
Multiplayer shows you what happened across your entire stack.
Multiplayer shows you what happened across your entire stack.
September 25, 2025 at 12:36 PM
Most “session replay” tools show you what happened in the browser.
Multiplayer shows you what happened across your entire stack.
Multiplayer shows you what happened across your entire stack.
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.
Because let’s face it: most developers don’t want to read static docs. Outdated Postman collections and PDF references slow everyone down.
September 11, 2025 at 3:59 PM
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.
Because let’s face it: most developers don’t want to read static docs. Outdated Postman collections and PDF references slow everyone down.
Dashboards are great at showing symptoms: CPU is spiking, latency is up, error rates crossed a threshold.
But when you need to understand why dashboards alone don’t cut it. 🧵
But when you need to understand why dashboards alone don’t cut it. 🧵
September 5, 2025 at 12:37 PM
Dashboards are great at showing symptoms: CPU is spiking, latency is up, error rates crossed a threshold.
But when you need to understand why dashboards alone don’t cut it. 🧵
But when you need to understand why dashboards alone don’t cut it. 🧵
What’s more expensive: developing a new API or fixing a bug?
August 29, 2025 at 3:29 PM
What’s more expensive: developing a new API or fixing a bug?
I wrote a feature that auto-generates a test script from a bug.
Basically: run the bug once, never write that test from scratch again.
Basically: run the bug once, never write that test from scratch again.
August 20, 2025 at 1:18 PM
I wrote a feature that auto-generates a test script from a bug.
Basically: run the bug once, never write that test from scratch again.
Basically: run the bug once, never write that test from scratch again.
Most monitoring tools give you summary data about a crash.
Very few help you see it in detail as if you had a dash cam.
Very few help you see it in detail as if you had a dash cam.
August 13, 2025 at 7:43 PM
Most monitoring tools give you summary data about a crash.
Very few help you see it in detail as if you had a dash cam.
Very few help you see it in detail as if you had a dash cam.
Reproduced a bug that’s haunted us for weeks.
Watching it unfold in a single timeline, with traces + request/response payloads + screens in one place…
Is this what closure feels like?
Watching it unfold in a single timeline, with traces + request/response payloads + screens in one place…
Is this what closure feels like?
August 11, 2025 at 1:56 PM
Reproduced a bug that’s haunted us for weeks.
Watching it unfold in a single timeline, with traces + request/response payloads + screens in one place…
Is this what closure feels like?
Watching it unfold in a single timeline, with traces + request/response payloads + screens in one place…
Is this what closure feels like?