2 ms·
> If it's complicated, then you're doing it wrong. You still need to do something even if you know this. Replacing the system is not an option, since the next
by Aeolun 4y ago
> If it's complicated, then you're doing it wrong.
You still need to do something even if you know this. Replacing the system is not an option, since the next one will be just as bad.
- londons_explore 4y agoNormally an overly complicated system is the result of: * evolving requirements over time (a rewrite fixes this) * A tech lead overcomplicating things for job security or to justify expanding the team or a promotion. This is rarely easy to fix, because typically now things will depend on crazy complex semantics... "We extended our pubsub system into a probabilistically lossy data caching layer!" I normally fix it by moving the project to 'maintenance mode' and reducing headcount to 0.5 or so. Obviously it's best to have enough oversight that that kind of thing doesn't happen in the first place.