3 ms·
we stress features over bugs I don't think we do. We stress the needs of the user over everything (and rightly so in my opinion). Often that means a new featur
by onion2k 9y ago
we stress features over bugs
I don't think we do. We stress the needs of the user over everything (and rightly so in my opinion). Often that means a new feature is more important than a lot of minor bug fixes, but equally a critical results-in-data-loss bug or an important security patch will take priority over any new features. It's just that those things are actually quite rare in production code, so it feels like features always take precedence.
- digi_owl 9y ago> We stress the needs of the user over everything Imagined needs of an imagined user perhaps. And more and more that imagined user is a drooling idiot best left in a padded cell it seems...
- onion2k 9y agoThere's no need to imagine what users need. There are plenty of great products to capture data about what they do in your app, and you can always talk to them as well. As for them being "drooling idiots", I find that if a user is getting something seriously wrong it's almost always because a developer or a designer built something that's failing at being easy to use rather than the user being at fault.
- watwut 9y ago> We stress the needs of the user over everything (and rightly so in my opinion). We don't. We stress whatever is hot on forums. And sometimes we stress whatever the most overconfident person in the room pushes for - regardless of whether that person has empathy for the user or not.