> Code quality matters, but the experience we provide matters more.
No it doesn't, in fact I would say, you can't have a good experience without good code quality.
Maybe you can release a few features with crappy unmaintainable code but over time the difficulty to add and release features increases exponentially. Your ability to serve the user's needs will then diminish over time.
Another big part of user experience is performance. You certainly can't have good performance without good architecture and well thought out code.
Front end development is a compromise, always looking to deliver best experience with the resources we have (developers time) with an eye on future maintenance. The stronger the coding practices of the development team the better experience we can deliver.
This post reeks of confirmation bias or at least the sample size is too low to draw any conclusions. What if that software engineer didn't want to progress his career and was happy at the level he was? What about those engineers that did go into management? I could be wrong but if you choose to stay in a roll a 30yo can fill why would it be strange that you would be expected to compete with those younger to get a job?
No it doesn't, in fact I would say, you can't have a good experience without good code quality.
Maybe you can release a few features with crappy unmaintainable code but over time the difficulty to add and release features increases exponentially. Your ability to serve the user's needs will then diminish over time.
Another big part of user experience is performance. You certainly can't have good performance without good architecture and well thought out code.
Front end development is a compromise, always looking to deliver best experience with the resources we have (developers time) with an eye on future maintenance. The stronger the coding practices of the development team the better experience we can deliver.