No, a good UI needs to serve the needs and wants of the user - not those of the developer.
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?
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'.