mitchm

"The problem isn’t simply that some of this content is written by machines. The problem is that much of it has no reason to exist other than to capture attention".

This has always been the worst part about the web, now amplified.

“ This is a test review from the debugging script. Please ignore it.” ?

I’ve also been exploring this idea. What if you could bring your own (or pull in a 3rd party) “CPU player” into a game?

Using an LLM friendly api with a snapshot of game state and calculated heuristics, legal moves, and varying levels of strategy in working out nicely. They can play a web based game via curl.

The personas were brutal in the best possible way. Great job

Worth reading The Creative Act by Rick Rubin. May help your relationship with side projects.

I should add, this is the instrumentation layer. You still send all the events generated to your event collection backend.

This all started with a simple question: when metrics are down, how do you know part of your application isn’t broken for a subset of users?

Production for the frontend is the user’s device, and we all know things can go wrong without an explicit error. With the current state of frontend observability tools, how do you tell when something should have happened but didn’t?

Too bad we can’t just have our users run `it('opens checkout modal on click', …)`, right? What if we could..

Maybe the world doesn’t need more HTML attributes, but it’s my best attempt so far at improving frontend observability. I think the ends justify the means.