@mattpocockuk Agents are incredibly good at gaming metrics. That’s why you have to point them at things that are objectively good for users, like lower memory usage, less CPU time, lower latency, less network traffic.
Number of PRs has zero correlation to UX.
100% agree: “Code is a strange shape-shifting substance because to a business it’s both an asset and a liability. If code is understood by no one in the org then its liabilities risk compounding faster than its value. If you are tethered to coding agents for making any progress then all your understanding is leased.”
https://t.co/nuHPRkCEer
UX latency is the most frustrating (lack of) advancement in computing over the last ~50 years.
IBM, way back in the 80s, found that user productivity shot up *exponentially* as system response time dropped. The "Doherty Threshold" was defined as ~400 milliseconds; the maximum amount of tolerable UX latency before interrupting user flow state.
It's unbelievable how many modern operating systems (*cough* win11) violate this threshold constantly.
Literally all you need to do as a Dev is pay attention. Add a "Doherty Threshold" to your test suite. There's so many different profiling tools, and especially with how good models are, really no excuse. Sure, some stalls are unavoidable, but that's when you pull out other UX tricks to at least give the illusion of responsiveness.
Crazy how much vintage computing hardware feels immeasurably more responsive despite having thousands of times less overall performance.