This issue was addressed in a similar post at a more specific level regarding the user interface.
I would like to touch on a more general level of design.
Every day I make design descriptions every day to ensure high quality. But from time to time I come across criticism with middle management and inexperienced developers on how to do things “right”.
Sometimes I just say: “Believe me, I saw how it leads, we do it differently,” sometimes I try to establish a scenario in which a certain set of options introduces problems, etc. Most when I feel like I’m not getting to the one I’m talking to. I could also say "trust me."
I believe that one of my abilities as a senior programmer should be explaining and motivating the technical decisions that we make as a company. I can do this at an economical and user level.
But I don't seem to be able to explain the technical and pseudo-technical levels, why some design options “feel wrong” and why others just feel more correct and useful, although at first it may be more difficult to implement or seem unnecessarily complicated.
Fortunately, I sometimes show good results, otherwise I will probably start to doubt the whole concept of good and bad design.
I would be interested to know what others are saying here.
Thanks in advance!
source
share