Uhhh, Enterprise? WTF? (Spoilers)

Um, yeah, so... Remans are on Earth in the 40s apparently aiding the Nazis. Or, is it the 22nd century? I dunno. Damn confusing.

Good finale, though. I'm looking forward to the 4th season next fall. Can't wait!

How big is yours?

Did the subject get you to look?

My iTunes Library size:
8479 songs - 27 days, 20 minutes, and 2 seconds - 37.77 GB

1346 tracks added in the last month alone. (Blame Nicole for most of those.)

Just got done sorting all of the new Nine Inch Nails stuff that got added, and then promptly went and bought most of it (used, of course).

Nicole and I share the iTunes library on a disk with permissions disabled. This allows us to both add music to the library and see it in our own separate user accounts (Mac OS X 10.3, by the way). The iTunes Library is shared, but we have our own preferences for the iTunes app itself. We use the grouping feature to separate tracks by username. It works pretty well, but the downside is that only one of us can really rate music. And, since I already rate everything, Nicole misses out.

Breaking it down a little bit further (I'm a bit obsessive about this, can't you tell?) yields these stats:

38 1-star songs
594 2-star songs
2225 3-star songs
1790 4-star songs
678 5-star songs

5199 AAC encoded tracks
3279 MP3 encoded tracks
1 Audible encoded track

692 tracks purchased from the iTunes Music Store (mostly by me)

251 songs have been played in the last day
2358 songs have been played in the last month

Smart playlists are cool.

System administration 101

1. Never perform a major system upgrade on a Friday afternoon (or Friday, for that matter). If it goes wrong, it is unlikely (unless your SLA says otherwise) that your vendor will be able to provide a fix for you by the end of the weekend.
2. Know your support contract. Again, if your SLA (service level agreement) says support is only to be provided at specific hours, don't expect it otherwise.
3. If you're performing an upgrade, make sure you back up your configuration beforehand.
4. Never tell the support agent that you're "really good at [insert Unix system here]" if you didn't perform #3 above. You'll be put on mute as your support analyst goes to laugh his ass off.
5. Realize that if your upgrade fails and requires a hardware replacement, you will not get it until Tuesday because your vendor won't be able to ship it until Monday.
6. Your vendor's developers are people. If it's a gorgeous 75+ degree day in Seattle, they'll do whatever they can be out of the office at 3pm.

Yes, I ran into a customer yesterday who must've not been paying attention during his sysadmin course. He, as a result, will not have a working server until Tuesday at the earliest. Should the upgrade have failed? Of course not. Should he have been performing an upgrade on a Friday? Of course not. A bad situation all around.

I wish developers would build in a time check in their upgrade tools (that'd be run against a server in their timezone). It should prevent upgrades on Fridays after noon. It should only allow upgrades Monday thru Thursday, realistically...

So anyway, the first month and a half at the new job has been going well. I'm still working hard to learn the products, and I think I'm making progress. It doesn't hurt that I have a good background in Linux support, so there's been less of a learning curve. I'm feeling good so far. Yay me.