Tip of the day. When there's network maintenance going on, don't try to test your work remotely (like from home at 11pm on a Friday). Why? You application will behave as if it's on crack. You'll wonder why. You'll debug. You'll become completely mystified.
Then you'll remember the announcement from earlier in the week. The one about the pending network changes on Friday night.
*sigh*
At least I didn't waste too much time.
It must be time to go read weblogs.
As much as I bitch about slashdot being a pile of crap (not the technology or the people behind it, but the idiots who have nothing better to do than "first post", "natalie portman's titls", and "Linux rulez! Microsoft/Apple/Sun suck", there's some good comments to read today. Of course, I read with a threshold of 4, so I tend to "miss" all the real crap.
Anyway, here are the stories: How Should You Interview a Programmer?, Mac OS X Switcher Stories ( which points to Tim's article), and Mac OS X 10.2 "Jaguar" Reviews Pour In.
I'm trying to get back into riding on a regular basis. I came home a bit early from work last night and went for a 45 minute ride. It felt great. So I convinced myself to do the same this morning before work. I'm so glad I did. I fell a lot better during the day after I've had a ride in the morning.
The weather this morning was excellent. It was just cool enough that I wore a light jacket when I left my apartment--must have been 56-58 degrees out. Clear skies and nice warm sun. Once the ride was about half over, I was warm enough to take it off and just enjoy the weather.
I've gotta keep doing this until the rainy season starts...
New rule. I no longer read or respond to e-mail that doesn't have a Subject. If someone can't take the time to briefly summarize that their message is about, why should I take the time to do it?