3 ms·
There is also the corollary that if you have a feature that no one uses then make sure it works before deciding that your users don't like it. A feature can be
by BWStearns 10y ago
There is also the corollary that if you have a feature that no one uses then make sure it works before deciding that your users don't like it. A feature can be awesome in its desired form but if it's janky as hell or unreliable then it won't get used. If the implementation sucks it's not proof that the feature sucks.
- granos 10y agoThe contrapositive would then be that if you find some really janky/unreliable feature that people are using, it must be pretty important to them and you should tread lightly when modifying it.
- BWStearns 10y agoTrue. I should have specified that the volume of use for poorly implemented features is only not useful for determining that it is a bad feature. Lots of use indicates that it may be a great feature, or that it's not the feature you thought it was (https://xkcd.com/1172/ https://xkcd.com/1172/)