2 ms·
Hm. I've always thought that building for the hacker/expert is a mistake, because it means building for someone who is willing to invest more time in figuring o
by jrochkind1 7y ago
Hm. I've always thought that building for the hacker/expert is a mistake, because it means building for someone who is willing to invest more time in figuring out what your software can do for them and figure out your UX (and has more skill at doing so) than many, and you're going to wind up with a UX that less expert non-hackers find confusing and too hard to figure out, and give up on without finding value.
The hacker/expert understands the problem domain better than most (expert), and is willing to invest more time in figuring out how to find value in the software (hacker) than most users. Unless you only want to target hackers/experts (which you can if you think there are enough of them), it seems dangerous to your UX to focus on them.
Am I wrong?
(Focus, at first anyway, on those who will get the most benefit from the product "whether they realise this yet or not" -- seems unproblematic good advice to me).