3 ms·
Could have been, yet isn’t. The first few were accurate and somewhat funny, but it quickly went downhill. Maybe developers aren’t the audience; we are more fac
by mosselman 8y ago
Could have been, yet isn’t. The first few were accurate and somewhat funny, but it quickly went downhill.
Maybe developers aren’t the audience; we are more factual and concrete whereas designers are usually more driven by emotion. The quotes in the article are not very accurate and seem made up, but the general emotion of “designers be like” is evident. Maybe designers respond to that emotion rather than bother with the accuracy of the anecdotes.
- dvtrn 8y agoyet isn’t. You know better than the person who wrote this list, and directly said it in fact is satirical at the conclusion--or is it just a disagreement of what constitutes satire like a few other posters have expressed? Personally I chuckled and grinned wryly at several moments in the piece, understanding completely where the author was coming from.
- zbentley 7y ago> [developers] are more factual and concrete whereas designers are usually more driven by emotion. I am so tired of this trope. Bad designers are influenced by emotion in unconstructive ways. So are bad engineers. I'm also tired of the "emotion == bad when doing engineering stuff" trope. The ideal for developers or designers (or a whole lot of other fields, probably excluding nuclear-launch executors and munitions testers) isn't some emotionless data/spec-driven automaton: it's a responsible person who operates pragmatically and calculatedly when they have enough information, and whose feelings/emotions are constructive and lead to good outcomes when information is scarce or snap decisions need to be made.