Interesting idea - thankfully in CSI, it is not required for the detective to have prior murdering experience. It might be more accurate to call the software engineering counterpart Dexter SE :P
All of this happened, because some time ago, we had such a massive deficit of engineers, so everyone got employed, no matter what skills or formal/informal education they have. Good practice or patterns wasn’t enforced, because employees were scared that they would lose developers.
I would argue that hacky code happens even in the best teams. The main vector of hacks sneaking in are requirement modifications to an existing codebase. The process looks like:
Interesting idea - thankfully in CSI, it is not required for the detective to have prior murdering experience. It might be more accurate to call the software engineering counterpart Dexter SE :P
I would argue that hacky code happens even in the best teams. The main vector of hacks sneaking in are requirement modifications to an existing codebase. The process looks like:
(I just updated my handbook Programming Without Anxiety with a chapter on Bugs and Debugging)
New system gets designed, interactions with neighboring systems mapped.
New system gets implemented, hopefully tested, etc. After some unavoidable early bugs, it runs just fine in production.
Small new feature request pops up. Think of it as the final straw. Even if small, it can turn the whole design upside down.
Guess if the whole system will be redesigned for the new feature to nicely fit, or if it is hacked in at some semi-convenient place.