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

101–110 of 172 posts

Re: UX clichés

#101

Post by msla »

zoul wrote: post #70
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…

UX for laptops/desktops was solved in the early 2000. In the early 2000, my music library was a few dozens GBs played back using mpeg123 or something. Nowadays it’s a Google Play Music subscription. Things have moved to the cloud, a lot. That’s a huge change in how computers work, requiring some serious UX changes. I too hate gratuitous UI changes, but things need to keep evolving.

In the 1950s, cars were made of steel and essentially designed to survive impacts by sacrificing the passengers. These days, they're identical fiberglass mice which fold up into a protective cocoon around their passengers on impact. You know how people drove cars in the 1950s? Steering wheels and some number of pedals. You know how people drive cars now? By calling an Uber, the drivers of which use steering wheels and some number of pedals.

So... why hasn't the fundamental UX of the automobile evolved in the past half-century?

Re: UX clichés

#102

Post by msla »

DonHopkins wrote: post #96
TeMPOraL wrote: post #67

Earlier quoted context omitted.

Come to think of it, if Henry Ford could , he probably would design a faster horse. The idea would have a lot of both business and practical sense - it would be improving a known tool, necessary infrastructure and network of services already existed, zero fire hazard, self-driving of level 4 autonomy out of the box. He (and people before him) designed automobiles, because that was the only way we could get the speed…

>zero fire hazard Didn't a cow start the Great Chicago Fire?

> Didn't a cow start the Great Chicago Fire?

That's the myth, yes. It might be true, it might not:

https://en.wikipedia.org/wiki/Great_Chicago_Fire

> The fire started at about 9:00 p.m. on October 8, in or around a small barn belonging to the O'Leary family that bordered the alley behind 137 DeKoven Street.^[4] The shed next to the barn was the first building to be consumed by the fire. City officials never determined the exact cause of the blaze,^[5] but the rapid spread of the fire due to a long drought in the prior summer, strong winds from the southwest, and the rapid destruction of the water pumping system explain the extensive damage of the mainly wooden city structures. There has been much speculation over the years on a single start to the fire. The most popular tale blames Mrs. O'Leary's cow, who allegedly knocked over a lantern; others state that a group of men were gambling inside the barn and knocked over a lantern.^[6] Still other speculation suggests that the blaze was related to other fires in the Midwest that day.^[1]

Re: UX clichés

#103

Post by DonHopkins »

open-source-ux wrote: post #28

Not a UX cliche as such, but a frequently used phrase: A carefully curated collection of resources Translation: a list of links Even better if you can shoehorn “hand-picked” in there ( A hand-picked collection of curated resources to help you learn [technology] ) Presumably the hand-picked links are always preferable over the, er, robot-picked ones. I wonder what a real museum curator must make of it all (I presume t…

Hand crafted artisanal RSS feeds. Each character of text and markup and every URL laboriously typed into Notepad as raw XML, without the use of copy-and-paste. Sorry if it doesn't validate!

Re: UX clichés

#104

Post by DonHopkins »

justcodebruh wrote: post #12

while we’re on the topic of UI/UX does HN have any recommendations for primers on the subject?

How about this anti-primer:

http://hallofshame.gp.co.at/qtime.htm

Interface Hall of Shame

- QuickTime 4.0 Player -

Amid much fanfare, Apple recently released a beta version of the QuickTime 4.0 Player. Intended to showcase the technological improvements of the QuickTime 4.0 multimedia technology, the QuickTime 4.0 Player sports a completely redesigned user interface. The new interface represents an almost violent departure from the long established standards that have been the hallmark of Apple software. Ease of Use has always been paramount to Apple, but after exploring the QuickTime 4.0 Player, the rationale behind Apple's recent "Think Different" advertising campaign is now clear.

Re: UX clichés

#105

Post by whoopdedo »

itronitron wrote: post #73
thereyougo wrote: post #2

My favorite “If Henry Ford had asked people what they wanted, they would have told him faster horses” Used as a counter-argument to the previous statement, when you start to realize you won’t have time or money to do enough user research.

>> “If Henry Ford had asked people what they wanted, they would have told him faster horses” I don't buy that, many people probably would have said that they wanted a horse that doesn't poop

Or eat. Or die of old age.

And I was going to say he delivered on that. Except now the horse poops carbon monoxide and eats gasoline instead of oats. But while cars also don't live forever except with great care, they do at least have a longer lifespan than a horse.

Re: UX clichés

#106

Post by bobbyi_settv »

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…

> DON'T FUCKING CHANGE THE INTERFACE

That's why it's important to have good UX people to help you get it mostly right the first time

Re: UX clichés

#107

Post by ivanhoe »

I find it amusing that his final disclaimer how "This is a satire article" really falls under the "if you have to explain a joke, it’s not that good"...

Re: UX clichés

#108

Post by mikeash »

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…

You don’t necessarily need automated tests, but you absolutely do need to test your tests. With any new test, I always verify that 1) it passes with the fix 2) it fails without the fix. Many programmers skip step 2 and it’s a good way to end up with tests that don’t test what you think they do.

Re: UX clichés

#109

Post by mikeash »

bdcravens wrote: post #60
sys_64738 wrote: post #36

Earlier quoted context omitted.

In other words, untested code is broken code.

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

In my experience, error handling code is often completely untested by any means.

Re: UX clichés

#110

Post by mikeash »

jasonhansel wrote: post #30
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

I could add an entire 10-page rant about people who insist on the Liskov substitution principle.

I never heard of the LSP being at all questionable. Can you elaborate?
Post reply on HN