Some days, the code flows, and the system gains power and depth you never expected. And, some days, you spend twelve hours of coding to get back to where you started.
Yesterday was one of the bad ones. I'm struggling to isolate system-dependent code in Tinderbox, moving toward Tinderbox for Windows. The easy parts are pretty much done, now, and yesterday began with a simple little file issue that snowballed into a code avalanche. So, four hours later, I backed out, and tried to remove the last-remaining bit of obsolete LArray code -- the section that sorts attributes and notes. An easy, obvious bit of refactoring.
Six hours later, the new code was working almost as well as the old.
Jeffrey Radcliffe reminds me why we're doing this:
I've been a wee bit busy this week, and I apologize for falling off the face of the earth. The end is in sight, and the work is paying off. I, for one, am looking forward to not dreaming about data structures for a few days."
In a pinch, Tinderbox has come through as a worthy task management system; I don't think I'd be sane without it. My organizer document keeps track of the hundreds of loose ends, and it allows me to spend me more time coding and just the right amount of time documenting.