Comment by account42

6 hours ago

No, a good UI needs to serve the needs and wants of the user - not those of the developer.

No, a good developer needs to anticipate the needs of the user. The ones they didn't even imagine. And then fix the system and take out all the garbage.

  • Maybe, the correct approach is not 'predict everything' and not 'have users tell you what they need', but something more akin to:

    1. have defaults 2. have ways to change defaults 3. have dev actually have an interest in the actual workflow, because while you can anticipate a lot, real use case will carry the day

    I played with a 'sound editing software via prompt' the other day, and there was still crazy how much distance there was between 'what i think i want' vs 'what i actually apparently want'.

  • Only a narcisist thinks he can adequately anticipate all needs of the user.

    • ONLY a narcissist? Are you sure? Do you... perhaps... always consider yourself sure?

      What about maybe like, a developer who actually talks constantly to their users and spends half the day emailing with them 7 days a week? Would that person maybe not be a narcissist and still be in touch with what their users need? Maybe even capable of anticipating a majority of their needs?