What's with all the superfluous cursing? Is that a shtick? Kind of dilutes the conversation.
Or strengthens it.
Regardless, it's just wording. Maybe see if you're attaching too much value to a combination of letters/sounds. Cursing happens a lot in life, so maybe getting used to it will let you handle it better and get distracted by it less?
(Just flipping the thought process here, mean no offence.)
The main problem I have with it is while I can appreciate the sentiment and the "power" of the tone, it makes sharing it with different audiences in a public forum much more difficult.
Passing the link to friends, outside of the office is much more straight forward (presuming I know them well enough). However, passing the same link to my team at work, where I don't have as long-term a relationship with or know their real level of tolerance is a lot harder to justify.
My tolerance to shock titles is one thing, but I don't really want to have an uncomfortable conversation with someone else who I shared it with that has a completely different level of tolerance.
If I were to quote your comment, and add in the phrase "heh, look at this piece of shit", does that make my comment a good comment? A critical comment?
That's what these guys did. For example, go to the part about the iOS scrolling dropdown. There is some grain of valid criticism in there, but they chose to call it "a piece of shit" and say "erm, wow, can't think of a better element for this" -- it's arrogant and shallow. They sound like Beavis and Butthead up there instead of UI or UX experts, which is unfortunate... because I hate dropdowns too.
And just a note I was thinking about while writing this: I believe guys like Draplin and Monteiro, as examples, give (typically great) profanity-laced talks and speeches but the difference is if you take the cursing out of their stuff you still have an interesting piece of criticism or advice. I sadly have the opinion that the same thing isn't true here.
I don't mind the aggressive tone, it's good for our field to have our own Johnny-Rotten-channeling-Don-Norman.
What I do mind is when the title stands in the way of the content, as the title of his book The Best Interface is No Interface.
That title was so puzzling to me, until I read the first snippet of the book where he redefines interface to mean graphical interface.
A graphical user interface isn't the solution to all design problems was too long to fit the cover, I guess
I was expecting more conversation around steppers, segmented controls and other alternatives. I agree that dropdowns suck, but I am disappointed with the lack of solutions presented.
Luke Wroblewski has a done some great research into dropdown alternatives. http://www.lukew.com/ff/entry.asp?1950
Where Luke's article directly talks about solutions. This talk is planned to be humorous in a way, taking things lightly. 2nd half of the talk focusses only on alternatives and how drop downs can be used better.
blocked @ work because this is pornography apparently.
Over 46 minutes long. I pity the people who had to sit through that presentation.
For those who didn't make it to the 18:00 mark, that's when they start talking about alternative solutions.
Humorous and helpful!
Hit my company's firewall for the first time ever clicking this link..
That talk was not helpful, nor did it really sell its case against their use. The reality is, they are the most effective element in CERTAIN cases, and others they are not. Use them wisely.
Thanks for your helpful comment.
I think it's meant to be a "bit" and humorous. It's quite clear to any designer that what they're referring to isn't specific to dropdowns, but poor form design in general.
Pretty much exactly what is said in the talk. They also give examples of modified dropdowns for certain cases that make them a lot more usable.
I lost it at "...as toothbrush designer, DEE-IT-TER Rams once said..." XD
I watched this a few days ago and has come to mind several times since then. Perhaps a bit sensational in title and in the beginning, but there’s some good food for thought in there.
Tell these to developers and watch them go between completely ignoring your suggestions and having a tantrum.
I wish in real world, I could design anything I want without "technical restrictions" of developers talking about.
That was awesome.
Alice Bartlett gave a great talk on this, based on proper user research she did at Gov.uk https://www.youtube.com/watch?v=CUkMCQR4TpY
When I see their first solution - using overall usage pattern based on statistics to create default or eliminate options - I can't help but thinking about "design is political" and "when you are prioritizing something, you are de-prioritizing others at the same time"