Gregory's Server@devxvda I think that it depends on the code, and how old it is. I'm having to work with some very bad code that is 10 years old, only ten years but those are ten years of bits of updating shoved in there anyhow on a deadline. No one knows how it works. At this point doing updates takes 90% effort to untangle the spaghetti mess enough to even make an educated guess of where to put the update... And you never, ever know for sure what unexpected side effects you're introducing...
|
3 comments
 @alter_kaker @uncanny_kate Ten year old code is a LOT different to fifty year old code. I have stuff from a decade ago still running. Not great code, but does what it needs to. Fifty years ago "quarterly goals" didn't exist. It was ready when it was ready, because to do otherwise would cost half the company.  @devxvda yeah. The old code jokes in my experience are more about 10-20yo code than 50. But my experience is pretty much all in retail and stuff like that |
@devxvda I asked a veteran colleague a question about the DB naming scheme and he laughed at me
@uncanny_kate