4 ms·
I was just thinking this. The home team loses some control over their architecture and might gain tech debt this way, especially if different teams have differe
by barbariangrunge 3y ago
I was just thinking this. The home team loses some control over their architecture and might gain tech debt this way, especially if different teams have different development philosophies and preferences.
Plus, you lose a ton of time implementing features outside your area.
Your away team didn’t know that those 5 functions had to happen in order, due to a timing issue nobody could figure out, so your code to change how a panel animates is now breaking unrelated calculations somewhere and causing data loss. You blame the home team for having bad architecture, but then learn a different group of three different away teams set that up and nobody can figure out how to clean it up because of the ripple effect bugs. There be dragons