Archive for the ‘work’ Category

Punt!

Friday, October 17th, 2008

Of all the diversions of life, there is none so proper to fill up
its empty spaces as the reading of useful and entertaining authors.

- Joseph Addison

It’s been a hell of a couple weeks. I’ve been professionally violated by security and process auditors repeatedly over the span of the last few weeks, experienced one of the most exhausting on-call shifts ever last week, and have been running around in a seemingly endless state of tired and really annoyed for most of the month of October.

Since I haven’t had a chance to write much recently, I’m going to attempt to make up for it by directing you to the blogs of a couple people who have.

Drew’s Walkabout Blog

I’ve known Drew virtually for at least several months. Maybe longer; my sense of time has always been a little screwy. In any case, he’s a pretty amazing guy, and meeting him in person at this year’s Burning Man was definitely one of the high points of my trip.

Recently he’s been doing a trek to various fascinating parts of the globe and documenting them in his always very intelligent, insightful way, and I’ve really enjoyed keeping up with his travels. He’s also one hell of a photographer and his legs look amazing when he wears a skirt, but don’t tell him I said that.

World Wide Jeb

If you’re into queer, beer-swilling, Aussie metalheads, I have some good news: one actually exists. If you’ve ever followed that filtercore link at the bottom of the page you’ve already been introduced to the author of World Wide Jeb. He’s just started the latest incarnation of his blog, but I think I can guarantee it’ll be worth reading; Jeb is, without exaggeration, one of the most consistently hilarious writers I’ve ever had the pleasure of reading. I have to be extremely drunk and have someone spin me around ten times and point me at a cliff before I get one-tenth as funny as Jeb is on an off day, and I’ll never look as good in a purple mohawk as he does. I secretly hate him for all of that, but he’s a great read anyway.

Bowling for Cholesterol

Sunday, August 17th, 2008

A few months back, when we were practicing for the second annual HP bowling tournament, my team had finished off a few pitchers. Someone got the idea that we should bet on the next game, with the loser taking the winner’s next on-call shift. I felt bad for Ken, since Dave was the other loser and was working for Facebook, and not very likely to care much if Ken’s phone was waking him up in the middle of the night.

It’s become a regular thing since then. The next time we all went bowling together, the bet was USDA Prime steaks for the winners, to be provided by the losers. Though the best Dave and Scott could do was USDA Choice and (oh, the horror!) Select, it was a pretty good dinner nonetheless.

The next time out the stakes were increased, and we were bowling for a steak and lobster dinner. Jimmie, Alan, Ken and Frank outdid themselves that time, and my team ate pretty well after that one.

Of course, since we were bowling again last night, the subject of a bet came up again, twice. The first time was for shrimp, and the second time for clams. Now, once again, I’ve got another seafood dinner to look forward to.

You may notice that my name hasn’t appeared on the losing side in any of those bets. Part of it is that my bowling average has been gradually increasing over time — but, to be completely honest, I still suck. If there’s one factor to which I can attribute the credit for earning me three dinners so far, it’d be Brian’s handicap negotiation skills. I’m relatively sure that, at this point, the two of us are the only ones left undefeated, and I’m giving him all the credit. Well, most of it. It’s not just that Brian’s good at negotiating a handicap; a lot of it is also due to Jimmie’s total inability to recognize a bad deal.

So, thanks, Jimmie. Alan and Frank, too. Rest assured that we do realize you guys don’t completely suck at bowling… It’s just that Brian’s smarter than all of you.

Arrrrrgh! Brains!

Wednesday, October 17th, 2007

I’ve been pretty bad about keeping this place updated lately. I’ve been in head-down, all-work mode for the last month or so, as my team and I at the ol’ place of employment try to build out two new data centers in time for the holidays, and it hasn’t left much time for frivolous things like blogging, relaxing, or sleeping.

It’s not that things haven’t been relatively interesting lately. I’d go into the details of all the little mundanities of my life over the past several weeks, but I’m almost totally decaffeinated at the moment, and I really don’t trust myself not to babble incoherently if I try.

The big news right now, though, is that a very dear friend is finally out of the hospital after what seems like an eternity there. He’s probably reading this, being the excellent Internet stalker that he is, so I’ll spare him and the other two people who will ever read this the embarrassment of a sloppy, tearful “welcome back,” and just say that I’m glad you’ve recovered enough to finally get the hell out of there. I missed you.

I’ve got to get ready for work, so that’s all the updating for now… I should be back to a regular schedule sometime around the second month of 2008.

Zzzzzzzzzz…

Sunday, August 12th, 2007

It’s been a particularly busy month here, which has contributed to my extended absence from this place. Between work, a couple side projects, and a couple small visitors from France (no, that’s not a euphemism), it hasn’t left me much time for the important things like keeping a blog updated.

mattfavicon.jpgToday I had every intention of correcting that, since I have a little downtime here, but I’m a little farther down than I’d expected. I’ve been spending the last couple of days coughing, sneezing, and pounding shots of NyQuil in a feeble attempt to fight off a particularly nasty cold. All I’ve wanted to do for the last couple days is sleep, and I’ve done a lot of it. Other than a few brief waking periods caused by a hyperactive pager (I’m also on-call at work this week), I’ve been asleep since around midnight Friday. It doesn’t exactly make for riveting blogging, as you can tell.

80 Minutes to Freedom

Wednesday, May 23rd, 2007

It’s been a very long week.

outdoor-clock-11892tch.jpgI’ve been telling people for a while that it was going to be a rough summer for me. I’ve got two data centers to help get online by the end of July, a few other fairly large projects I’m working on, and enough turmoil at home to suck up the rest of my time. Those, however, have nothing to do with why I’ve been so wiped out this week.

The guy who was supposed to have taken last week’s on-call shift at work had other commitments, so I volunteered to fill the spot. Normally, I’m pretty lucky. All hell can break loose before and after my on-call shifts, and I usually find myself sitting happily in the eye of the hurricane. This week, probably because it was really not my turn, karma came back and slapped me in the ass.

It was all pretty typical stuff: the usual storage outages, server crashes, and general large-scale website hassles. This time, though, everything was just a little more severe than usual, and I spent a few sleepless nights babysitting misbehaving hard drives to keep them running, chasing down people who didn’t realize the site was down so I could have them restart it, and trying to log into machines that wouldn’t let me in.

At one point — I think it was Friday, but it’s all a bit fuzzy now — I actually ran out of steam went face-down into my desk. I’ve taken naps on the job before, but that was the first time I’ve ever been in the middle of something and just passed out from lack of sleep.

Fortunately, my shift ends in 80 more minutes, and I’m going to be happy to hand it off to whichever poor bastard’s next. Of course, nothing will happen for the next week and I’ll look like a pussy for complaining about it, but it was real, I swear. I saw it. I was there. Most of the time, anyway.

A Prayer for Jon Ginoli

Friday, April 20th, 2007

I’m thoroughly wiped out. A team of us were up until 3:00 am trying to get a working network out of the tangled mess of routers and cables the contracting client keeps in their data centers, with only a small degree of success. A very small degree. In other words, things are still pretty screwed up. “Things,” in this context, would refer both to the network and my sleep-deprived brain.

Pansy DivisionMy spirits have been kept afloat, however, knowing that I’ll be seeing my beloved Pansy Division tomorrow night at CafĂ© Du Nord (and by the constant reminders from my best Portuguese friend that it’s right around the corner).

[Aside: I live in the U.S.A., so I'm an American. People from Canada are Canadians. I know a few Frenchman, some Mexicans, and assorted Englishmen, Scots, and Irishmen. What the hell do you call someone from Portugal? A Port? Portsman? A Portuganean? Wait, I know: a Portugasque.]

Anyway, I’m not going to let a few dropped IP packets get me down.

The Pansies are my favorite; I shall not miss them.
They maketh me jump up and down in dark mosh pits:
They singeth to me of Deep Water.
They restoreth my Political Asshole:
They leadeth me to Touch My Joe Camel for Denny’s sake.

Yea, though I drove to the Silicon Valley near the campus of Apple,
I will fear no packet loss: For my Pansies art with me;
Thy Dick of Death and thy Two-Way Ass, they comfort me.
Thou preparest for a gig before me in the presence of the Cocksucker Club;
Thou annointest my ears with Vanilla; My Groovy Underwear runneth over.

Surely Headbangers and Hippy Dudes shall fill all the space of thy venue,
and I will dwell At the Mall forever.

Musings on a Side Job

Thursday, April 19th, 2007

You know a network’s bad when, after digging, poking and prodding at it for a couple weeks, you still can’t figure it why, at least sometimes, it works.

I’ll be driving to the south bay after work tonight to rip it apart and rebuild it into something someone who’s been doing networking for a couple decades can understand.

Amateurs… They shouldn’t be allowed near routers.

Decision Made.

Sunday, April 8th, 2007

As of yesterday afternoon, it’s official. I won’t be taking the new job.

There are a lot of reasons for that, from some questions about the financial health of the potential new place to my reluctance to give up working with one of the best teams I’ve ever been on, among other factors, but I’m pretty happy with the decision. All in all, the whole thing’s definitely worked out for the best.

With that out the way, I had some time yesterday to think about more important, things, like that the lease on my Crossfire is ending in a couple of months. It just so happens that when I made the call to say I was staying at my current job, I was near the strip of car dealerships in Oakland. Coincidence? Probably not.

The Crossfire’s been a great car this last three years, but it’s going back to the dealer tomorrow. I need to clear a spot in the garage.

hpim0667.jpg hpim0669.jpg

Did I Accidentally Sleep Through 2007?

Monday, April 2nd, 2007

I just received an email notifying me that “all … offices will close from Monday, December 24, 2007, to Friday, December 28, 2007. In other countries that observe Christmas as a company holiday, … offices will close for similar period at that time.”

Do these people not realize it’s barely friggin’ April here? Am I supposed to start planning for the holidays now? Does anyone do that?

There should be a law against mentioning Christmas before September, at the earliest. I feel violated.

war_on_christmas.jpg

Hosed.

Tuesday, March 27th, 2007

Yesterday was a bad network day. It started with a slow link from one of our websites out to our most obnoxious clients. Those are always the tough ones; if a link’s dead, it’s usually pretty obvious where things are screwed up. When they’re just intermittently slow, it takes a little more detective work and some actual thinking to pin down what’s going on. Fortunately, I’d received some good data from the client (a very rare occurrence) and was pretty sure I had it pinned down to one of our ISPs’ routers.

Anyone who’s worked in networking can tell you that’s where the battle starts. No provider anywhere, regardless of how big or small they are, wants to admit the problem is on their equipment. It’s just one of those rules of the Internet: it’s always the next guy’s problem. So, even though I had evidence that their router was hosed, the ISP jerked me around for the entire day trying to prove I was wrong. They finally surrendered at around 6:00pm and actually looked at the router I’d told them was broken at 10:30am, and whaddaya know? It was hosed.

HosedThen there was the other gigantic client who’s been trying to get a point-to-point line working with us for months. I’ve had the thing set up and ready to go for so long I don’t even remember when I did it, but I get pulled into conference calls every few days where they try to tell me I’ve either put in incorrect firewall rules, bad routes, or any number of other things I haven’t done. There was another one of those calls yesterday, and I watched another couple hours of my life drain away while I sat on a call with their firewall guys, their network guys, their QA guys, and a handful of random managers answering all the same questions yet again. At this point I should just have them dial into my voicemail, and tell them “Press 1 for me to tell you the routes are there again. Press 2 to hear me say the firewall holes are all open. Press 3 if you want me to beg you to check things out on your own damn network again before dragging me into another boring conference call.” Fortunately, this time someone with a clue was actually on the call, and whaddaya know? Their routing was hosed.

Just when I thought I was done, though, I got home and the potential new employer needed some firewall configuration done. I hopped on the boxes as soon as I got home and started poking through them to see how much work was going to be involved. About 15 minutes into flipping through the configurations, my sessions locked up. Then the pages started coming. Apparently, the box I was looking at had just crashed, and took their website down with it. I made a few phone calls, trying to explain that I knew what had crashed, and that even though I’d been on the box at the time, I hadn’t done anything to crash it. That’s not a position I like to be in — it just doesn’t look good. After that it took another hour to get things working again, and in the end it looks like their equipment is underpowered, and I’d just been lucky enough to be logged into the firewall at the same time someone else was bring up enough new equipment to cause a hiccup on the circuit that sent my box into a seizure. It took about an hour of phone calls, reboots, and crossed fingers to get everything working again.

You know, it’s days like yesterday that I start reconsidering the decision to become a computer guy instead of an English teacher. At least when you’ve got a pissed off teenager threatening to shoot you, you know exactly what you’re dealing with.