3 ms·
Here is my issue with people who come up and say "you could do X a different way and it would be objectively better for your use case" (note this is in a larger
by cortesoft 10y ago
Here is my issue with people who come up and say "you could do X a different way and it would be objectively better for your use case" (note this is in a larger organization with lots of different teams, and I am talking people from other teams):
They often don't really understand my use case. They only hear one part of what my team is trying to do, and then act like they know what I need. Yes, your suggestion works for the use case you know about, but not for the 10 other use cases I need to design for.
Second, these considerations were usually already considered while we were planning this work, and there is a reason we decided to do it a different way. I don't have time to re-explain why we chose to do things the way we did to 10 different people who come to me and ask why I didn't choose to do it this other way.
- gravypod 10y ago> They often don't really understand my use case. They only hear one part of what my team is trying to do, and then act like they know what I need. Yes, your suggestion works for the use case you know about, but not for the 10 other use cases I need to design for. So then can you not say "but I also have REQUIREMENT_X for this project? Do you think that your solution will mesh with this other need I have?" If you can't have a technical discussion defending why you feel your solution is the best then you must not be confident about your solution.
- cortesoft 10y agoIt's not about the ability to defend my solution, it is the time it takes to do it. My team is very busy with lots of things, we don't have time to re-explain why we are doing it this way to ten different people. We DO explain and defend our solution, to our boss and invested stakeholders, but we don't have time to do it again for every random guy on the other teams.