2 ms·
Unless the proponents of competing ideas are actually lying to management[1], there should be distinguishing characteristics that allow a reasonably savvy manag
by snowwrestler 12y ago
Unless the proponents of competing ideas are actually lying to management[1], there should be distinguishing characteristics that allow a reasonably savvy manager to make a decision. One does not need to check code into the repo regularly to understand the conceptual differences between two different architectures.
In the case where there is not enough data to make a reliable decision, the proper management move is to instruct both teams to collect more data, through load testing, user research, beta trials, etc. A well-known example of this was the early iPhone software development, in which one team built off the iPod OS and another off the Mac OS, until the best way forward became clear.
If the disagreement is not likely to be decidable with data, then it's probably a matter of opinion anyway, and a quick decision that sticks is better than agonizing.
[1] If you think your staff is lying to you, there are bigger problems than technical competence.
- deleted 12y ago[deleted]