Comments by "Traveller" (@traveller23e) on "Ctrl-Alt-Del: Learning to Love Legacy Code - Dylan Beattie" video.

Good legacy code is wonderful. It never breaks, it gives you insight into a whole different world, and sometimes a chuckle when you find a comment that just says "TODO: fix this mystery bug" from 1996. I do however take complaint with a completely different class of code, originally written with the primary objective of time to market, designed by an architect in a rush and an unclear idea of the end goal, and programmed by people who were being clocked by the minute in their implementations of vague requirements. Those sorts of codebases tend to be atrocious, even if they follow MVVM or some other modern pattern to a t.
5
@seancpp Especially since a lot of the requirements are arbitrary business needs rather then technical ones. It would be nice to have some easy marker in the code to say "nothing bad will happen if you change this"
2