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.
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.