Comment by dieortin
3 days ago
> One colleague said slowing down does lower your error rate, but mostly because you're doing less of everything
That’s not how rates work
3 days ago
> One colleague said slowing down does lower your error rate, but mostly because you're doing less of everything
That’s not how rates work
They aren’t claiming that the doing less by itself changes the rate in this sentence. They are saying that the rate changes when you slow down, probably due to having more time to focus, which in my opinion is likely.
Haha, yeah.. Also with most real world, vs LLM FOMO hype fantasy land, consumer software has two very real tiers of bugs; regressions, and bugs in new features.
Regressions are usually the absolute worst.
Up to now we've just been eating shit on the DX side as far as regressions in Codex and Claude Code because everything is all "go-go-go OMG I don't want to fall behind" and also.. Access to new models is tied to harness updates.
But a ton of industries have users that are not so willing to eat the regressions in the name of more features and changes than they can keep up with.
Edit: Also moving too fast.. You may have been less likely to "get it right" than ever before leading to design churn. Again, depending on industry and users, they may not be very tolerant to releasing the 5th complete overhaul of some feature in so many weeks..