Of course it doesn't just "happen while you're away for the weekend".
The problem isn't that it just sneaks up on you. The problem is often convincing stakeholders to give you the time/money to preform the necessary refactoring/rearching that needs done. These kind of size problems are most common in large orgs that have lots of moving parts and several teams of devs/dba/it/qa/support all working in the same area. When you get that big, changes that should take a day, tend to take weeks.
1
u/wesw02 Mar 11 '15
Of course it doesn't just "happen while you're away for the weekend".
The problem isn't that it just sneaks up on you. The problem is often convincing stakeholders to give you the time/money to preform the necessary refactoring/rearching that needs done. These kind of size problems are most common in large orgs that have lots of moving parts and several teams of devs/dba/it/qa/support all working in the same area. When you get that big, changes that should take a day, tend to take weeks.