Kris Jenkins - Slaying a UI Antipattern

[@krisajenkins]

"We'll talk about [category theory] in the bar afterwards." I can confirm that yes, we did. Lots. :-D

[@higherorderfunctioning]

sooo jealous

[@TankorSmash]

Enjoyed the talk, very well delivered. Looking for more of your talks now!

[@datawhining1200]

Great talk! :)

[@kanagarajm3628]

Top notch talk! I would love more viedoes from this guy.

[@ShisuiElric50]

Love this guy's voice, he should make a course on something, I would buy it to just listen to him lol

[@abdulachik]

hilarious and insightful, great talk

[@wchen2340]

Honestly i was hoping for something different. Disclaimer : Maybe its just me but : i'd summarize this video basically as "please sanitize your (user)output ... just as u do with (user)input". Which is a valid point indeed. The good thing about it is that it can be fixed/tackled with proper patterns (and imo even implement unit tests that reveal those ui fails ) as demonstrated in the video. I appreciate pointing out the issue and approach how to fix it alot. The bad thing is theres something going on with UI designs that id really like to see addressed, though having trouble to verbalise ill describe it as : abusive usage of the interface to the user to "make him do/take notice of" something. Or a more polemic statement : Its the users interface to your application. Not the designer/developers interface to the user". Its a little bit like dark patterns that emerge though not beeing intented but counterfeit the user experience due to the lack of respecting the context/enviroment the interface exists in. The "slayer" is still alive....

[@Nathankthanks]

Who knew Gaius Baltar was so into elm?