Hacker News Reader

Comment by vijucat | Hacker News Reader

> Windows Desktop Experience Team from Win7-Win10. Starting around Win8, the designers had full control, and most crucially essentially none of the designers use Windows.

How are they allowed to do this? This is awful and goes completely against the "eat your own dog food" philosophy.

Separately, I've noticed that developers in general are too deferent to designers, who then get to run amok with shitty ideas. Your pushback is exactly what is needed.

View on HN

Pushback will get you a bad review, smaller bonus, and a performance improvement plan. The company has been too dysfunctional for too long. Fixing it would be like boiling the ocean.

Counterpoint: Different competencies. A UX designer telling a developer how to code would be laughed out of the room, the other way around is the same.

Difference being, the software (at least more or less) works; what's annoying people is the usability and consistency of the UI[1].

Designers deserve to be laughed out of the room; developers don't.

___

[1]: Until they get their shit in order, designers can kiss my ass for their pretentious "UX" claptrap. The actual experience is only max-half interface, min-half functionality. Where the latter is provided by lowly coders.

Hi, the equivalent here is not a UX designer telling a developer how to code, but rather telling the developer their code does not work. For example, "Hi, I clicked delete in Windows Explorer, but the file was not deleted". This is just user feedback.

To design the core UX for a system, you should understand its userbase. If you're stuck in a paradigm where there are documents instead of applications, where closing things doesn't terminate them, and where the default switching hotkey doesn't allow you to switch between windows of the same application, it affects how you perceive the whole system and puts you at odds with your user base.

Reply on news.ycombinator.com