Legacy code revisited
I have asked "what is legacy code?" and the answers I got could be broken down into two categories: 1. some measure of age, and 2. some measure of maintainability because of maintenance.
The code I am working on definitely falls into the second category. The codebase was started around 2005, so any reference to age can be ignored. However the initial design was not thought through at all, therefore all the code added since then has been patched onto the existing codebase. Refactoring is common because of the high maintenance costs.
This is what I have to work with. It is a fun product, and I hope that there are better corners of the code to peek into, but until I see that the code I currently work on falls into category #2 above.