11–20 of 172 posts
““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.
My favorite is “users don’t read” being used to create blog articles that are 125 words of nonsense when the topic needs 1500.
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
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 be tested?
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.
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!
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 dicking around with the design -- the content is what matters" or "it doesn't matter how beautiful it is if no one cares about you're saying."
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…
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
The 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…
It could also be good old fashioned regular satire, too...
The 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…