Comment by cromka
3 hours ago
Problem with legacy code is that with time some of the bugs have become features without users even knowing it or remembering it.
3 hours ago
Problem with legacy code is that with time some of the bugs have become features without users even knowing it or remembering it.
Yeah you can not deploy this to customers with the hardware already in production if it mass fixes bugs and improves behavior because those are likely breaking changes.
They have to modernize the code while keeping all weird edge case behaviour. I think this can be done. And I suspect that is probably the request.
The issue is deciding what is weird edge case behavior and what are bugs. It can be a fine line.
https://lawsofsoftwareengineering.com/laws/hyrums-law/
Of course there's a law for it!
Thanks!
Every bug is someone else's workflow: https://xkcd.com/1172/
Also, extensive commenting inside codebases is useful documentation, incl. these kinds of incidents. Good code documents the how, but not why. Comments shall also include the "why" where applicable.