UI editing is a professional job
blog.jgc.org
blog.jgc.org
In a large pharmaceutical company with 10,000 employees, you have people with job titles like "Quality Assurance Lead II (Wound Management)". In a startup with 3 people, people call themselves CEO, CTO, and CFO. As the startup grows, it will need people. Eventually you'll hire a "QA Lead II" or "UI Editor (Web-Apps Division)". The main question is who do you hire next? Do you need a graphic designer more than a helpdesk person? Do you need a project manager more than an AP assistant?
The same is true of UX design. But the problem is while the distance from programmer to sysadmin seems to be a short walk, the distance from programmer to UI/UX from my experience is a long one.
Sure, we cannot/should not afford another guy with a title, but Graham is pointing out a valid blindspot for all of us and it should be taken into account when making decisions.
Your development environments, your film editing software, your database software, your programming languages, your unix shells, etc should under no circumstances be intuitive, because that also means they can never be powerful which is more important.
Think of musical instruments. A kazoo is beginner-friendly, but you can only make fairly simple sounds with it. On the other hand, a piano keyboard is barely usable at all to a beginner, but is incredibly powerful in the hands of an expert.
If a task is complex, it takes a good amount of insight to be able to divide it into such specific contexts without unduly getting in the way of the user.
Real life, despite being mind-numbingly complex in its entirety, can be easily interacted with because we break it down into a number of simple intuitive interfaces and then switch in and out of which interfaces we're focusing on very rapidly. If we can emulate the same thing with software, then learning to use computers will be no harder to do than learning to use anything else in life.
I do agree that making the ui for complex tools easy to use is very difficult, but I wouldn't label complexity and ease of use a trade off. There are an infinite number of ways to display a user interface, and I believe there's always a way to make something easier to use.
I do agree that making the ui for complex tools easy to use is very difficult, but I wouldn't label complexity and ease of use a trade off. There are an infinite number of ways to display a user interface, and I believe there's always a way to make something easier to use.
I prefer not to use the word "intuitive" exactly because it has no definition and leads to such miscommunications. You're saying the layout of a piano keyboard is arranged by a system that is easy for beginners to understand. I'm saying it's not easy for beginners to use. These are two very different things and the piano is an interesting example of how one does not necessarily imply the other.
"the playing of music itself is unintuitive"
Most of the children I have met are able to use their voices and percussive instruments to play music. I don't think producing some form of live music is inherently difficult.
Of course, combining those simple tasks in complex ways will give you complex results. But then you've moved all of the complexity out of the tool and into your head, and beginners cannot do these things.
To go back to my instrument analogy, you can play a 2-hour song with 10,000 notes on a kazoo. But, you're only playing one note at a time. On a piano, you can play many notes at once, playing some simultaneously and others with partial overlaps, changing the sustain and timbre of the notes as you go. The kazoo, while it creates a song that is a complicated whole, does not perform tasks as complicated as the piano. This is what I'm getting at with my statement about software interfaces.
So yes, the complication of a piano comes from what you can do with the multiple simple interfaces, not from the complexity of the interface -- see where I'm going?
On a computer however, there's complexity in whatever the task is, and that's inherent. You can't fight that. But you can fight the complexity in the interface itself.
There's been plenty of articles on HN about interface inconsistencies. The windows 'system tray' is particularly notorious, where basically every single icon does entirely different things depending on whether you left click, right click, middle click, double click, etc. Imagine a piano, where the notes hit by the keys are in a random order on every piano. And it's not a windows only problem -- interfaces are consistently inconsistent on every platform.
How so? What are you learning how to do with the hammer? Pry up nails? Hammer nails?
What thickness of nail should you use to go through a given board? How should the way you hold the nail differ depending on size of nail, size of board, working area?
A hammer is not at all simple; it takes just as long to get the hang of than your average desktop app, if not longer.
The only exception I can think of right now (3D Studio Max) essentially has too different modes: a normal mode where you have to use your mouse to select everything (which takes a really, really long time) and an expert mode without any buttons at all (which is by no means intuitive).