Comment by K0balt

The furious pace of Ux “optimisation” that we see across the board (and especially at AI companies) is a hidden anti pattern. The time and frustration of learning a new ux is an acceptable burden when it frames real new capabilities or workflows. It’s not good to rework your ux user experience every week just because you can.

Not only that, but AI is categorically terrible at ux review. I don’t mean aesthetics, I mean attention flow, workflow in general and what the user anticipates as a logical path to feature discovery and exploration. Increasingly, features are hidden behind workflows that meet a single use case but fail to be universally logical or in many cases, even accessible at all outside of the test case.

So, people… use AI in code review. It’s actually pretty great at it if you do it right, and you can ship better software with fewer bugs than ever before. But please, don’t pressure your ux guy to “10x” with AI. In fact, now that you are “10x”ing your development cycle, you are probably going to need to hire -more- ux developers if you don’t want your product to feel like slop even if it’s gold under the hood.