3 ms·
> But it still makes a shitty user experience to do something that is counter to what your users expect and want. One way to improve shitty user experiences is
by jacques_chester 8y ago
> But it still makes a shitty user experience to do something that is counter to what your users expect and want.
One way to improve shitty user experiences is to study them. This requires information.
How do I answer questions like: what is the most frequently-used command? Which command causes the most people to give up? Which argument is being asked for, which already exists? What effect does a change in documentation have? How many projects do people work on and do we need to invest in tools for repositories with many projects?
Etc etc.
This is all Product Management 101: form hypothesis and test it.
- ptx 8y agoYou could answer such questions the usual established way it's normally done in other fields: sample a voluntarily participating statistically significant subset of the population.
- jacques_chester 8y agoOther fields do this when there is no better alternative. It's is orders of magnitudes more expensive and also, more to the point, quite unreliable.
- ringbugger 8y agoWould be great to give the user an option to send statistics or something like that to do just that. I really like VSC. But things like this really question all the positive experience. I doubt product management is going to help here. Will now scan network transfer VSC is causing. In many other cases I wouldn't even bother anymore.
- jacques_chester 8y ago> Would be great to give the user an option to send statistics or something like that to do just that. This is exactly what they do.