Snore

[bookzombie]

A very long, 11 hour+ working day today. My projects for the next release are ready to go into system testing, so I was doing what we call 'Design Validation', which means that the Lead Designer has to do some brief tests on the code to ensure that it at least roughly does what is required.

I'd blocked the whole day out for this, which would have been sufficient if my plans had not been scuppered by the fact that the code wasn't ready until about half past two in the afternoon.

The process did prove its usefulness, though, when I found several project-killing errors in the code (unit testing, what unit testing...). Luckily they were careless (probably due to a rushed development time) and thus fairly easy to fix, rather than 'Oh my god, you've totally misunderstood what you have been asked to build!' sort of errors which are more serious.

In fairness, this sort of thing doesn't happen too often.

But more of the same tomorrow as we started late.

Do you know, the thing I hate most about working late is that you get home in time to eat and then go to bed (pretty much). Bleugh!

Comments

[cabell.livejournal.com]

Yeah, and I just can't do it--go to bed, that is. So if I get home late, I know I'm going to be screwed on sleep because I can't GO to sleep until I feel like I've received an appropriate amount of winding down time.

[numbat.livejournal.com]

Working evening shift as I do I'm quite familiar with the problems working late can cause even though I don't usually go to bed right away. Evening work has its advantages but it's a hard taskmaster.

[bibliofile.livejournal.com]

During crazy times, one company I know defined the start of the next working day as twelve hours after you left. At least people got a token amount of downtime, there. It's worst when it's several days in a row.