Arron Young

Dashboards are loud. The signals that matter are usually quiet, and I'd like to collect yours.

I've written here before about how our most active users at Murror turned out not to be our happiest ones. That changed how I read numbers. Sessions, streaks and retention curves all measure that people came back. None of them tell you whether coming back was good for them.

Since then I've been more interested in small, quiet signals that are hard to put on a chart. Things like a user who stops using your product because they no longer need it. Someone who writes in to correct a detail, which means they read closely. A person who recommends it with a caveat, because they're being honest about who it is and isn't for.

My own rule of thumb is that a signal is worth trusting when it would still look good if you were wrong about your product. A big engagement number can rise because people love something, or because it nags them. A quiet signal like "they told a friend, unprompted" is harder to fake, even by accident.

i'm alim, one of the makers of agentmash. we launched today and i keep going back and forth on one design call.

in august two of our agents collided on payments code. fixing prod OAuth took 10 hours. worktrees keep agents out of each other's folders, not each other's code.

We re testing whether agents can discover a site s docs from its homepage, and what happens when API endpoints require authentication. Those are different problems, but both can make it hard for an agent to verify what a site supports.
How are you making your docs and APIs discoverable today? Do you link docs in the HTML the server sends, publish a public schema or read-only endpoint, or take another approach? What s worked for you?
We re building Dedica to check whether agents can access and use websites. If you re exploring this too, here s the page: https://www.producthunt.com/prod...