Sometimes, we can intuitively tell that certain approaches have issues. However, due to the client's existing workflows and habits, the main challenge is raising awareness.
Communicating this can be quite exhausting—it can take half a day just to explain why something should be done a certain way. And if the client has a strong sense of pride, they might even find it offensive.
So, I think it’s all about balance. Sometimes, I choose to stay quiet and observe first, then bring it up only when necessary—like when a revision is expected to take a lot of time.
As a result, I often end up delivering something rigid or not entirely satisfying, but as long as it meets the requirements and works fine, that should be enough. In software engineering, chasing perfection can easily become self-destructive.
Top comments (0)