Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

UX clichés

uxdesign.cc

Post reply on HN
Print view View original

51–60 of 172 posts

Re: UX clichés

#51

Post by Udik »

Waterluvian wrote: post #11
dylanrw wrote: post #7

““Designers should have a seat at the table” When you are not able to prove your strategic value to the company based on your everyday actions and behaviors, and you have to beg to be invited to important meetings.“ Or it could be that an experienced designer has more to offer than acting as a glorified crayon only putting color where the stakeholders want it.

It's satire. But it's also speaking to the idea that designers who make meaningful contributions won't need to ask to be at the table.

Frankly, I've been in jobs where I was about the only one who made meaningful contributions, and I still had to beg to have a seat at the table. Which they didn't give me. So I know from experience that making meaningful contributions is not sufficient nor necessary to be involved in the decision process.

Re: UX clichés

#52

Post by normalhuman »

I am not a designer nor a software engineer, nor a business person. I am just a (heavy) user of all sorts of software for a very long time. I am a competent coder, and I code for research and pleasure. I don't have a dog in this, let's say, professional race.

Every time I spot "UX" in relation to something I use, I cringe. Not because I have anything against the idea of design, or good interfaces, or designing good interfaces. That is all great. The problem is that 99% of the time that the term "UX" shows up in connection with something I use, two things are going to happen:

1) I will have to relearn how to do something that I already was used to doing without even thinking;

2) Some feature or option is going to be removed.

The human brain is incredibly plastic and adaptable. Unless the interface is truly absurd, most people can get used to it and never give it a second thought again.

My number one (by far) request as a user:

DON'T FUCKING CHANGE THE INTERFACE

Unless there is a very good reason, and I bet there isn't.

I bought my first MacBook in 2007. Thankfully, Apple is one of the best behaved companies when it comes to not changing things for the sake of it, and part of the reason why I stick with them. I don't mention this out of some sort of fanboy-ism (I have no loyalty to corporations, I just buy shit I like). I mention it to make a more important point:

The UX of 2007 was absolutely fine, and if they would have made zero changes since then I would be perfectly happy. UX for laptops/desktops was solved in the early 2000. Everything else since then is just irrelevant bullshit.

Re: UX clichés

#53

Post by damontal »

AlexTWithBeard wrote: post #3

I'd love to see a similar list for software engineering. - if your code isn't important enough to be tested, it's not important to be written - every function must fit a single screen

Single screen eh? Is that why I see all the devs at the office with their screens turned sideways?

Re: UX clichés

#54

Post by [deleted] »

normalhuman wrote: post #52

I am not a designer nor a software engineer, nor a business person. I am just a (heavy) user of all sorts of software for a very long time. I am a competent coder, and I code for research and pleasure. I don't have a dog in this, let's say, professional race. Every time I spot "UX" in relation to something I use, I cringe. Not because I have anything against the idea of design, or good interfaces, or designing good i…

[deleted]

Re: UX clichés

#55

Post by sys_64738 »

normalhuman wrote: post #52

I am not a designer nor a software engineer, nor a business person. I am just a (heavy) user of all sorts of software for a very long time. I am a competent coder, and I code for research and pleasure. I don't have a dog in this, let's say, professional race. Every time I spot "UX" in relation to something I use, I cringe. Not because I have anything against the idea of design, or good interfaces, or designing good i…

>My number one (by far) request as a user: >DON'T FUCKING CHANGE THE INTERFACE >Unless there is a very good reason, and I bet there isn't.

This x100.

Re: UX clichés

#56

Post by dkarbayev »

normalhuman wrote: post #52

I am not a designer nor a software engineer, nor a business person. I am just a (heavy) user of all sorts of software for a very long time. I am a competent coder, and I code for research and pleasure. I don't have a dog in this, let's say, professional race. Every time I spot "UX" in relation to something I use, I cringe. Not because I have anything against the idea of design, or good interfaces, or designing good i…

> iOS 7

> Touchbar

Re: UX clichés

#57

Post by swiftcoder »

usea wrote: post #14
AlexTWithBeard wrote: post #3

I'd love to see a similar list for software engineering. - if your code isn't important enough to be tested, it's not important to be written - every function must fit a single screen

- if your code isn't important enough to be tested, it's not important to be written Does this rule cover all code? Do your tests, which are code themselves, not need their own tests? If not, what is special about a test that you know it's correct, when there is no faith in in non-test code? Is it possible to write your program entirely out of the special "test" code, so that it's always correct and doesn't need to b…

One finds a truly surprising number of bugs in tests and test frameworks. So yes, your tests need tests.

Re: UX clichés

#58

Post by 1023bytes »

dkarbayev wrote: post #56
normalhuman wrote: post #52

I am not a designer nor a software engineer, nor a business person. I am just a (heavy) user of all sorts of software for a very long time. I am a competent coder, and I code for research and pleasure. I don't have a dog in this, let's say, professional race. Every time I spot "UX" in relation to something I use, I cringe. Not because I have anything against the idea of design, or good interfaces, or designing good i…

> iOS 7 > Touchbar

Or the courageous removal of the 3.5mm jack

Re: UX clichés

#59

Post by falcor84 »

chiefalchemist wrote: post #43

I'm feeling that cliches is not the right word. To call something cliche generally means it's over-used, tired, boring, etc. But the article itself is not saying that. Perhaps maxims or truths, would be better?

All of these are very much overused to the point when people don't really think about then any more, and as the article implies, they are often used to dismiss arguments by referring to some vague wisdom.

Re: UX clichés

#60

Post by bdcravens »

sys_64738 wrote: post #36
AlexTWithBeard wrote: post #3

I'd love to see a similar list for software engineering. - if your code isn't important enough to be tested, it's not important to be written - every function must fit a single screen

In other words, untested code is broken code.

Except almost no code is untested. It's just typically not tested via $approvedProcess
Post reply on HN