yep, the bug triggers when a political party overflows its buffer. The funny thing is, the system still catches the error and spams the logs with FATAL error messages, but the system has been throwing them for so long and seems to still be chugging along so we kind of ignore them. One of the original devs made a comment about how someone should fix it right before leaving the team. Anyway, the effect tends to accumulate, so if you deploy it to prod and don’t fix it, eventually you get… this.
It’s related. All over the codebase different devs have put in catches for it, but often as not instead of handling it they just wrap it in a new warning, dump it to the log, and move on. Dwight wanted to decouple those modules, correctly, but he didn’t know how because the reason they’re coupled in the first place is because we didn’t handle this problem correctly in the initial design, so he slapped a warning on it and called it good enough. Every once in a while some hotshot dev comes in with a proposal that exploits it (and introduces tons of technical debt that we don’t see because we don’t measure it) and because it looks good for the shareholders the PR gets approved and merged. If they’re lucky then they get promoted out of development, or occasionally fired, but in either case the problem in the code gets exacerbated and never really fixed.
Trying, I’m stuck on a bridge with some of the seniors right now. One of them wants to “just push through and see what happens” and roll forward with the change, the other one disapproves but clearly has no idea what else to do. Nobody seems to want to even propose a plan because then they’d be on the hook for it, so we just keep going back and forth and not. ending. the call.
yep, the bug triggers when a political party overflows its buffer. The funny thing is, the system still catches the error and spams the logs with
FATALerror messages, but the system has been throwing them for so long and seems to still be chugging along so we kind of ignore them. One of the original devs made a comment about how someone should fix it right before leaving the team. Anyway, the effect tends to accumulate, so if you deploy it to prod and don’t fix it, eventually you get… this.My bad.
wait, this is the log Dwight wrote that keeps spamming “military industrial complex”?
It’s related. All over the codebase different devs have put in catches for it, but often as not instead of handling it they just wrap it in a new warning, dump it to the log, and move on. Dwight wanted to decouple those modules, correctly, but he didn’t know how because the reason they’re coupled in the first place is because we didn’t handle this problem correctly in the initial design, so he slapped a warning on it and called it good enough. Every once in a while some hotshot dev comes in with a proposal that exploits it (and introduces tons of technical debt that we don’t see because we don’t measure it) and because it looks good for the shareholders the PR gets approved and merged. If they’re lucky then they get promoted out of development, or occasionally fired, but in either case the problem in the code gets exacerbated and never really fixed.
Fix it Fix it Fix it Fix it!
(I tried to find the Futurama meme of that, but my phone said No)
Trying, I’m stuck on a bridge with some of the seniors right now. One of them wants to “just push through and see what happens” and roll forward with the change, the other one disapproves but clearly has no idea what else to do. Nobody seems to want to even propose a plan because then they’d be on the hook for it, so we just keep going back and forth and not. ending. the call.