3 ms·
> by catering to the use cases of the common man, you're limiting them to your interpretation of what the common man's use cases are. Or, using telemetry, user
by cwyers 10y ago
> by catering to the use cases of the common man, you're limiting them to your interpretation of what the common man's use cases are.
Or, using telemetry, user studies and more, you can actually figure out what those use cases are. It's not rocket surgery.
- TeMPOraL 10y ago> Or, using telemetry, user studies and more, you can actually figure out what those use cases are. It's not rocket surgery. Or you end up convincing yourself into thinking your own preconceptions are actually the real use cases. It's like social science, except most software development companies haven't heard of any kind of scientific rigour. Not to mention the study tools are broken on purpose too; it's not unheard of that people writing e.g. analytics / A/B-testing tools optimize them for the "wow it works" aspect - successfully, because most companies using them don't know squat about stats. That said, even if you identify the right use cases, there's the orthogonal aspect of whether your tool will allow for those and only those use cases, or if it is a more general one.