Phil and I have been working on cleaning up the PRIDE codebase. It's long overdue for a good overhauling because as we've been doing this exercise, we've found a cubic assload of code whose only apparent purpose is to be tested (meaning that it's only used in the unit tests, but nowhere else in actual production code and as such, is completely useless, really).<\/p>\n
So for the last few weeks, I've been combing through 191 java classes (35562 lines of code), pruning out bits of junk, improving code structure and usability and generally going nuts. <\/p>\n
It's tedious work because as soon as you fix something in one place, you need to cascade the changes to everywhere else that uses the bit of code you just re-wrote. It's the worst type of IT work: one that is boring as hell but requires a lot of concentration to figure out what stuff you wrote 6 months ago (or worse, was written by somebody else) is supposed to be doing and how it should use the improvements you're making as you go along.<\/p>\n
At least I have the gay dance to keep me sane.<\/p>\n","protected":false},"excerpt":{"rendered":"
Phil and I have been working on cleaning up the PRIDE codebase. It's long overdue for a good overhauling because as we've been doing this exercise, we've found a cubic assload of code whose only apparent purpose is to be tested (meaning that it's only used in the unit tests, but nowhere else in actual…<\/p>\n