Wednesday, I had to go back to the darkroom to get the bulk of my printing done because we're coming down to the end of the semester and it had to be done. This, of course, meant taking time off of work again, as I already had to do so Monday.
I thought I was going to get to work in the darkroom all day Monday, but the class that comes in two hours after ours needed the darkroom. To further complicate things, I spent the bulk of the first hour I had to work trying to help a classmate that hadn't even started developing her film, which she never did because by the time she got everything together, it was five minutes until the end of class time. She had a class immediately after ours and they were taking a test that day.
I spent the next hour developing my roll of film and left Decatur. This was followed by some personal errands and then work for four or so hours.It Happens
Wednesday morning, I made a command decision. Instead of going to class at o' dark-thirty then waiting around for four hours until the other class potentially got out of the lab, I decided I'd sleep in (for a Wednesday) go into work for a few hours and then hit the darkroom. (I wound up working in the darkroom from 1320 - 2340.)whester
and I have lunch a couple of times a week. I asked if he wanted to take lunch really
early for the both of us - 1130. (We like to go between 1300 and 1400, but since I've been in Development they eat early  and I'm starting to pick up the habit.)whester
had been saving his money and really needed a new computer. He decided he was going to get a Mac Book Pro. He had settled on the 15" to get away from the Intel graphics; I convinced him to get the top line 15" model because it has 1GB of vRAM, was a better card all-around and would aid in increased performance because of OpenCL/CUDA and would also when cracking hashes.
So it was that he told me he couldn't wait any longer to once again have a beefy machine at home, so instead of going to lunch, we went to our friendly Apple Store. whester
became the proud parent of one hellava machine.
We parted company in the parking lot having driven separate vehicles. I went on to the lab and he went back to work. Because he needed to run Migration Assistant to move everything from his iMac at home, I told him that as much as he wanted to stroke and play with his new baby, he should keep it in the box until he had time to properly set it up. whester's new baby
The next day I went into work as usual. I got in extremely
early (like 0745) especially considering how long I had been out the night before. (Got in shortly after midnight.)
I told everyone in Development–and everyone else I met–that whester
had a new baby the day before and that everyone should go congratulate him. Now, I had hoped that he'd have a line of visitors trickle by all day long congratulating him on his recent acquisition. But as fate would have it, one of the developers BSODed his box. As whester
has been serving as a liaison for IT, whester
was called in to save the day.
Now, Development is a big room with no dividers, so when he walked in to perform his IT duties, whester
was congratulated by the entire department at once! The only two people that thought this was hilarious were whester
But the story doesn't end there. Now it's your turn. Go congratulate whester
on his new baby. He'll appreciate it.