|
|
|
|
|
by crtlaltdel
2324 days ago
|
|
ha! last year i was at a shop
that had a dev manager who snuck in a stored procedure into a prod db. the arch called for an instance per customer, with each using the same sprocs. when one customer suddenly had prod fails it caused all the teams who had pushed code to burn cycles tracing the issue (the effects were system-wide and this was the biggest customer). we diffed the sprocs and saw what was up. the correct code was restored and the problem got fixed. in the end the dev manager in question didn’t have much of a reason for making this change without telling anyone. |
|