3 ms·
I like this one: > UX should be a mindset, not a step in the process Mostly because it's not a UX-cliché, but a cliché for everything: security, accessibility
by Vinnl 8y ago
I like this one:
> UX should be a mindset, not a step in the process
Mostly because it's not a UX-cliché, but a cliché for everything: security, accessibility, UX, localisation, etc.; advocates want them all to be an essential part of the process, but in practice, nobody manages to do all that.
- TeMPOraL 8y agoIt's also true in so far that for some reason[0], people still think of building software like of an assembly-line process, which is wrong. Programmers are seen as construction workers, which is a wrong analogy; it's probably a cliché at this point to mention that in building analogy, the compiler is the construction workers; programmers are the people drawing up the blueprints. At the blueprint level, you have some level of back&forth between designers, architects, structural engineers, electrical engineers, plumbers, fire safety people, etc. Building software is like that. It's a high-dimensional optimization process in which all those concerns like UX, security, accessibility, etc. are each a dimension, and in which you initially only know the rough shape of the terrain, so you have to walk it to discover its features. Or, to use a different analogy - software isn't like assembling a car toy on a factory line. Building software is like everything that happens in between the CEO saying "we need to build a toy car" and the factory getting the BOM and designs. -- [0] - probably because it simplifies management.
- graphememes 8y agoPeople who say this, say it because they don't want to commit.