I only skimmed the article, but it was enough to ignite my fire and actually take the time to write up a response based in my experiences. I can say as a UI/UX

I only skimmed the article, but it was enough to ignite my fire and actually take the time to write up a response based in my experiences. I can say as a UI/UX specialist myself, a lot of terrible design is due to not putting enough thought into the design and/or not allowing UI/UX engineers to do their jobs. I will also say that UI/UX is very much an art as opposed to a science, and even the best designers can get it wrong or the final product will frustrate someone due to unexpected edge cases or accidental dark patterns. Some observations over the past two or so decades: - Not engaging enough with the customer, i.e., finding out what they actually and truly need as opposed to pandering to their egos because they’re SMEs or whatnot - Engaging too much with the customer by allowing them to have too much say in the design. I’ve seen it go so far as to allow the customer to actually make their own designs (wireframes or mockups, etc.) and then handing that off to the devs to implement, no questions asked, which ended up in a ton of rework for obvious reasons - Relying too heavily on frameworks by allowing yourself to believe that you MUST use one of their built-in widgets or patterns and not create a custom solution that makes sense for the use case - Somewhat contrary to the above, not relying enough on a given framework’s widgets or patterns which can lead to inconsistent design and UX and unnecessary reinventing the wheel - The use of so-called no-code or low-code solutions: Not that these are bad per se, but it leads to the fallacy that a non-engineer (usually mid-level IT manager or “system analyst”) can use these tools to create a complete or even somewhat viable solution (I speak from experience) - Sacrificing a good design for any reason, e.g., ad space requirements, various types of compliance (including even the virtuous ones such as Section 508) - Relying on a framework to do the UX for you, leading to another fallacy that you don't need a UX specialist UX research still very much needs to be a thing, and I don't say that because it benefits me (it does), but because I wholeheartedly believe in the need for it. I wouldn't design a house or even a pool without the expertise of an architect, so why would an entire dev team build a multi-million dollar UI without a UI/UX engineer?