- Knees : stabby
- Database code: not working 100%, but good enough to let QA start hammering it
- Due date: today
- Overtime: ending today
- Airplane: booked
- Weather: doubtful
- Other plans for weekend: massive amounts of sleep and TV watching
- Mood: cautiously optimistic
Category: Rant
Oops
I’m coming down to the wire of this database re-architecture task. I’ve been working 60 hours a week for 8 weeks now on this thing, and it’s due this Friday. Unfortunately, I have come to the stunning realization that there is a gaping problem in my design.
Continue reading “Oops”
Sigh
See this dialog? I’m seeing a lot of it. I’m working on a very large project, and this one particular file is the main GUI for our system. The guy who started it was in love with Visual Age For Java, and didn’t like splitting his stuff into separate classes, and after I took it over I’ve pretty much continued along the same lines, so this file is over 10,000 lines long. Yes, you read that right, ten thousand lines of poorly documented code.
Just about every word you type into Eclipse in this file either leads to a long delay as the CPU maxes out and the disk churns, or this dialog. I’ve tried quitting everything else to provide more memory for it to work in (you’d think 2Gb of RAM would be enough for Eclipse, Safari, iChat and iTunes to get along, and you’d be wrong).
Sigh.
UpdateOk, what sort of moron declares a method to throw “Exception”?
My irony meter exploded
Last night, in a parking lot I saw a bumper sticker that said something like “Live lightly so that others may live”. A great sentiment, except I saw it on a gigantic SUV. And not one of the semi-practical ones that looked like it was on its way to a cabin in the woods or was full of climbing gear and skis, I’m talking one of those pristine, shiny, leather seats and chrome monstrosities that never leaves the pavement.
Updates and backups
Well, after I got home I tried Adobe Fucking Updater again. This time it popped up a dialog saying “no updates to be installed” so quickly I didn’t even notice how much RAM it was taking. Certainly a far cry from hours and gigabytes of memory that it took when I ran it at work.
Also, I did a Time Machine backup for the first time in a few days. I’d started it in the morning, but it was taking too long so I’d aborted it after about half an hour. I started it again when I got home, and expected it to take 5 or 10 minutes like it usually does, or maybe a bit longer because I’d just installed the Leopard 10.5.2 and Graphics updates. Instead it ground and ground and ground and finally finished 3.5 hours after it had started. I’m told this is because the disk was nearly full, and it had to re-arrange old backups to discard the appropriate old ones.