The two aren't necessarily related. You can have great design and structure under the hood, with a crappy user experience.

I've chatted with developers that were confused when I've mentioned the user experience. Even though they've published their code, they have no intention of thinking about what the user has to go through, and don't care.

You can see a similar perspective when you use software with bugs in basic functionality, sometimes critical bugs, and the devs are focused on adding bells and whistles.

Reply to this note

Please Login to reply.

Discussion

We agree. What I'm saying is the other way around. If you have a good user experience, you need to maintain good code behind it otherwise the bad code will translate to a bad experience.

Good code can be an absolute pain to use. But I'd almost just call it bad code for that reason.

I've been surprised at some of the 'sketti code I've seen. Some of it was a great user experience, but you're right, it doesn't last. The nightmare of steadying an upside-down pyramid with ropes and poles catches up to the front end eventually.