@Da7_Tech That number counts changes, not people. A changelog moving that fast means whatever worked for you yesterday might not behave the same today. Has anything you set up there lasted a week?
@petergyang Calling it No Moat and then shipping it in two hours makes the point on its own. Was the second pass faster than the first, or did it fight you?
@danshipper@every A vibe check was never the soft option if you use it on real work. No benchmark ever told me if a model would follow my formatting twice in a row. What do the scores miss in your work?
@DamiDefi The building is the easy part. The contract one is where it breaks: you can't act on a flagged risk without reading the clause yourself, so you end up reading it anyway.
@AnatoliKopadze The 85% is Anthropic engineers, the group most likely to be doing that anyway. Outside that building, most people have not filled one chat window yet. Do you see the same gap?
@diegocabezas01 I keep one prompt of my own for this, a dull formatting job I rerun every few months. Same input every time, which is the only way I have noticed a model getting worse.
@Da7_Tech The handoff is the part that dies for me. The second model has none of the thread, so I paste the whole chat back in and after a couple of switches I stop. Do you pass a short brief or the raw conversation?
@pebb_io It stays useful only while the person writing it is the one who gets called when it is unclear. Lose that and it becomes a form filled in at the end of the shift.
@IterIntellectus The cleaner is going to be fine. Nothing on my desk changed the day any of those scores landed. What changed, months later, was how we write up a shift handover.
@Hesamation I keep getting stuck on the 100 versus 400. A faster admin never closes that gap. The fix has to be on the intake side, and I have never seen anyone manage that part.
Most of what I give a chat is dull. Renaming files, checking one list against another, nothing I would ever demo. What is the dullest thing you give it?
@AgenticOperator Where I get stuck is what happens when both pages sit in the same chat. Maybe it still picks the competitor. Have you watched one flip?
@0x_kaize Half the cards in that screenshot say free tier capped, phone required or card required. Useful as a directory, though free is doing some work in that headline.
@WarMonitorINTL Cloudflare and AWS were spiking on the outage boards in the same window. Four labs failing independently at the same minute is the less likely story.
@Ananth7e If that's what it turns out to be, the interesting part is who decides it's finished. A chat answer ends by itself, so most people have never had to write down what done looks like.
@AgenticOperator The asymmetry usually happens by accident. Writing specs about a competitor is easy, writing them about your own product means someone has to commit to numbers in public.
@wallstengine The last line is the one that stings. The email still gets written, it just takes the time it used to take, and most of us quietly forgot what that number was.
@danshipper You can fall back because you still know how. The people who started after these tools shipped have no manual version of the process to return to, which is a different kind of outage.