At least some of it (not all of it) will leak from devs pain to users pain... Untidy unaesthetic unreviewed code will sooner or later introduce inconsistencies, poor performance, and bugs, and as you get more of it, the harder it is to clean up properly and get things under control.

Code that is untidy and unaesthetic from a developer’s perspective is also likely to be confusing to a user and perform or scale poorly, in my experience at least.

Depends on how it manifests. If things change every app release sometimes for better sometimes for worse and nothing really stays consistent over time it is clearly bad for user.

Users really like stability of their experience. They want the things that are working to keep working. If something is bit weird but acceptable they expect it to continue like that. Going back and forth between things might be the worst. After bad bugs like data being lost or thing not working at all.

> developer’s perspective is becoming increasingly unimportant as LLMs become the main readers and writers of the code.

Until the LLM itself becomes confused by the 10 layers of old patterns that weren't fully deleted from the code base, 5 of which do more or less the same thing but in minutely different ways that cause issues.

Both. I debugged an issue a few days ago where a messy, incomplete migration was causing every agent that drove by to very confidently assert the wrong behavior and try to make breaking changes.

I mean that it's allowed more bad apps to be created. It hasn't lowered the quality of apps necessarily but the low barrier to entry means things can be created that don't need to exist