Tom Johnson
banner
tomjohnson3.bsky.social
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
‣ Shape your data early.
‣ Prioritize security.
‣ Be deliberate with receivers.
‣ Export with efficiency.
‣ Monitor the Collector itself.

The lesson I keep coming back to is simple: an observability framework is only as strong as its Collector configuration.
November 6, 2025 at 4:04 PM
He's giving a talk at ZurichJS next week.

If you're in town, I recommend checking out their EOY meetup on Thursday 13 Nov, 18:00 CEST. 👇

zurichjs.com/events/zuric...
ZurichJS Meetup: 1st Anniversary Special Edition | ZurichJS
Before the winter code freeze sets in and the only thing you want to debug is your holiday light setup, it's time for on...
zurichjs.com
November 3, 2025 at 10:52 AM
I bet a Multiplayer full stack session recording + Claude Code would have caught that 😉
October 16, 2025 at 5:26 PM
What about 'workslop'? That one would count too 😅
October 15, 2025 at 11:55 AM
How much time do you have? I feel like the risk zone is anywhere between 3-6 hours.
October 8, 2025 at 12:20 PM
Start simple, release gradually, and let user feedback guide you. Less is more when it comes to MCP.

❓ Curious what others are seeing: what’s the most *useful* MCP tool you’ve come across so far?
October 1, 2025 at 12:19 PM
For us, that meant focusing on two high-value use cases:

1️⃣ Fixing bugs (where we can pipe full-stack session data directly into an AI tool)

2️⃣ Building features (where annotations/sketches from a session replay add the needed context to AI prompts).
October 1, 2025 at 12:19 PM
Don’t just map your API 1:1 into MCP tools. That creates context bloat, and LLMs aren’t great at wiring together dozens of endpoints. Instead, scope tools tightly around developer intent.
October 1, 2025 at 12:19 PM