It's interesting to see professional development at work. I work at a place which doesn't do the standard release, work, test, relese cycle. It's a big continual system, so things kinda get added and fixed as it goes along. It's interesting to look at a code base which is the result of multiple programmers learning from their mistakes, but not having the time to go back and fix them (and certainly not learning from their peers' mistakes).

It makes a lot more sense now why development teams I've seen from the outside always viewed their past code with such revulsion...