4 ms·
Technically it’s actually a good idea …if you do it before publicly releasing and spending marketing budget on both products, giving them a full software lifec
by odo1242 1y ago
Technically it’s actually a good idea
…if you do it before publicly releasing and spending marketing budget on both products, giving them a full software lifecycle and a dedicated user-base that no longer trusts you to keep things running.
Honestly, even in that case it sucks to be a developer there knowing there’s a 50% chance that the work you did meant nothing.
- noisy_boy 1y ago> Honestly, even in that case it sucks to be a developer there knowing there’s a 50% chance that the work you did meant nothing. Does it have to mean nothing? If there is a review at the end of the exercise, good parts from each of the teams can be explored for integration to build the best final product. Of course all these things are probably as much political as technical so it is always complicated.
- odo1242 1y agoI was certainly thinking of the more political case where one team simply gets laid off with no review. That case would be perfectly alright, to be honest.