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.
UX clichés
31–40 of 172 posts
Re: UX clichés
#32Earlier quoted context omitted.
... that’s because the author clearly states, at the bottom of the article, that it’s satire.
> This is a satire article, where I use humor, irony, and exaggeration to invite reflection. Except good satire uses exaggeration to lampoon things that are (at least partially) true in reality . Whereas for half the examples here my reaction was, "No one has ever said that for that reason."
Re: UX clichés
#33Earlier quoted context omitted.
Everytime my co-worker tries to mention the "Pareto-Principle" (a.k.a. "Please let's not waste time on this, because it's frontend and I don't care about frontend") and "Single Source of Truth" (a.k.a. "let's expose our DB as directly as possible"), my soul barfs.
I’ve used “single source of truth” to explain what I like about Redux/the Elm Architecture. Yeah it shouldn’t mean anything about access or indirection but it’s still a decent idea, no?
Re: UX clichés
#34Earlier quoted context omitted.
Do those people think Ford invented motor vehicles? Before the Ford Motor Company ever existed we had a motion film of a trip to the moon, and they didn't go by horse!
Yes, I imagine no one ever thought to themselves a flying horse was the realistic way of getting to the Moon.
While not «realistic,» they did believe it was.
Re: UX clichés
#35Earlier quoted context omitted.
I'm thankful that the words "paradigm" and "synergy" have been mocked enough that business people avoid them now.
Now they are leveraging a lot.
Re: UX clichés
#36I'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
Re: UX clichés
#37Earlier quoted context omitted.
Now they are leveraging a lot.
Scaled agile is my current pet peeve. "Value Streams" and "Program Increments" and a "distilled" book that's 500+ pages.
Re: UX clichés
#38Re: UX clichés
#39The quoted aphorisms, in my personal experience, aren't used for the reasons being imputed. It feels like forced satire. For example: > "Content is king" - A pretty strong argument to convince everyone to push the deadline because you haven’t received the content that will go on the page you are designing. I've heard this a lot, but never from a designer trying to push a deadline. It's used to say "stop wasting time…
... that’s because the author clearly states, at the bottom of the article, that it’s satire.
Good satire is a form of pointed commentary. If you use it to say , "I didn't mean any of what I wrote", then you defeat the purpose of it.
Re: UX clichés
#40Earlier quoted context omitted.
Yes, I imagine no one ever thought to themselves a flying horse was the realistic way of getting to the Moon.
Ahem, actually: in norse mythology there was the flying horse «Sleipnir:» https://en.wikipedia.org/wiki/Sleipnir While not «realistic,» they did believe it was.