May 03

Creative jaywalking

My new IBM office is in a building near the intersection of Six Forks Road and Millbrook Avenue in northern Raleigh. Unlike the other IBM sites where I’ve worked, this one has no cafeteria — but that’s not really a problem, because there are plenty of restaurants and fast-food places nearby. In fact, some are within walking distance. A shopping center at this intersection includes a KFC/Taco Bell hybrid, a Subway, a Chinese place, and a restaurant called the Bull and Bear. (What kind of restaurant is it? A dismal one, apparently.)
Although it’s not far away, the shopping center is diagonally opposite the IBM site, requiring me to cross both streets in order to get there. Both crosswalks are equipped with WALK/DON’T WALK signal lights and push-to-walk buttons. After having made use of these crosswalks several times, I have learned something interesting: the signal light for crossing Six Forks Road always says DON’T WALK. I’m not exaggerating — you can stand there as long as you like, but WALK never appears. (Needless to say, pressing the P-T-W button has no effect.) The simplest explanation is that the crossing signal is broken, but I have another theory. I believe that the city’s traffic engineers studied the intersection and concluded that it is never safe to cross Six Forks on foot, so they installed a signal that won’t let you try it.
Of course I don’t let that stop me. Six Forks may be too dangerous for ordinary pedestrians, but I went to the University of South Carolina, where you either learn to dodge cars or you don’t live to graduate. USC’s main campus is located in the middle of downtown Columbia, and a major thoroughfare (Greene Street) runs right through the middle of the campus. This is by design, I’m sure — the university’s founders believed that natural selection should be a part of the curriculum. That also explains the Horseshoe, a large grassy rectangle dotted with trees and crisscrossed by brick walkways. There is no vehicular traffic on the Shoe, but on most days there are multiple impact sprinklers in operation. To traverse one of those brick walkways without getting wet, you must observe the timing of the sprinklers and then carefully choose the correct walking speed and moment of departure. It’s kind of like a live-action version of Pac-Man, and it helps you develop the skills you need to cross Greene Street.
The Horseshoe has a large squirrel population, which provides the opportunity for another entertaining pastime: Squirrel Bingo. The entire Shoe is your Bingo card, divided into triangular spaces by the walkways. The squirrels are your counters. If you can find a contiguous series of spaces, each containing at least one squirrel, that crosses the Horseshoe from side to side, you win. I lived on the Shoe for a year, and by the end of it, I could play Dodge The Sprinklers and Squirrel Bingo simultaneously. Compared to that, crossing Six Forks Road isn’t even a mild challenge.
UPDATE: Marie reminds me that Greene Street had gates that were used to close it to vehicular traffic and save students from being run over. True, but the gates were only closed during the daytime on weekdays; on evenings and weekends, it was back to Pedestrian Roulette. And in any case, the gates only protected a couple of blocks of Greene, from Sumter Street to College Street. If you wanted to walk to class from Sims (where Marie lived), or from the Presbyterian Student Center (where I lived during my senior year), you still had to dodge cars.
Marie also denies any knowledge of Squirrel Bingo, even though she worked on the Horseshoe at the South Caroliniana Library. That just proves that she was spending too much time on her job, and not enough time gazing out the window.
UPDATE: Bob reminisces about life on the Shoe.

May 01

Earthquakes and hit points

Listening to BBC Newshour on the radio this morning, I heard a report about the earthquake in Turkey. At one point, the reporter spoke with a British earthquake expert, and I realized that I know the guy. Well, sort of. I’ve never met him, and I was hearing his voice for the first time. But we actually exchanged e-mail messages a few years ago.
The reasons for this go back to 1979, when I was first introduced to Dungeons & Dragons by friends at the University of South Carolina. If you spent any time in game or hobby stores, you were familiar with a monthly magazine called The Dragon, published by TSR Hobbies (the same company as the D&D game itself). But there was another magazine, White Dwarf, that you could only find in a few stores because it was a British import (published by Games Workshop). Issue 15 (October/November 1979) contained an article called “How to Lose Hit Points . . . and Survive” by a British gamer named Roger Musson. I didn’t see that issue of White Dwarf, because the Columbia hobby shop where I was hanging out didn’t carry the magazine. But a few years later, while browsing in Silver City Comics (a much cooler store in Cayce), I stumbled across a copy of The Best of White Dwarf Articles II, a 1983 compilation of material from issues 15 through 30. I found several of the articles interesting and bought it. The Musson article was included, and I was particularly impressed by it.
Fast-forward to early 1997. A discussion of the hit point rules (and ideas for improving them) was in progress in the D&D newsgroup. I thought Musson’s article was relevant, so I posted a summary. To my astonishment, Musson himself responded, expressing delight that the article was still remembered two decades after he wrote it. I sent him a note praising the article and asking some nitpicky questions about it, which he was happy to answer. In the course of all this, I learned that he was now a seismologist working for the British Geological Survey. In fact, he seemed to be a rather prominent seismologist — at one point, I ran a Web search to see if he had a gaming-related site (he didn’t), and found numerous references to, and quotations from, his research.
So this morning, when a BBC reporter introduced an earthquake scientist named Roger Musson, I knew immediately who she was talking to. BBC World Service doesn’t seem to have an online archive of their radio reports, but this transcript of their report about Turkey’s last major earthquake (in 1999) includes some quotes from him. His remarks this morning were quite similar: he discussed the tectonic forces at work in that part of the world, and the Turkish construction practices that tend to exacerbate the death toll when a quake occurs.
Thanks to the BBC, a great many people heard Musson on the radio today. But how many of them know that he used to play D&D, have a copy of his article about hit points, and have conversed with him by e-mail? I’m such a geek.
(Note: The Dragon exists today as Dragon Magazine, now published by Paizo Publishing. White Dwarf is also still around, and is even still published by Games Workshop. But it’s now devoted entirely to miniatures-based wargames like Warhammer.)
UPDATE: You can listen to the BBC radio segment here. Dragon Magazine‘s print edition ceased publication in September 2007, but the magazine lives on as a part of the D&D Insider website.

May 01

Moonlighting

Readers of this blog may be starting to wonder: does this guy ever write about anything other than his job and/or lack of one? That’s a fair question. When I created this blog, I didn’t define a specific subject for it. The idea was to post whatever I felt like writing, on whatever topic happened to be on my mind. In recent weeks, that has been employment. But really, what else would you expect? The major events of my life have all been job-related lately: starting a temporary job, changing shifts, getting inquiries about IBM contracts, interviewing, receiving an offer, and starting the new contract. As I settle into my new job and it becomes just another part of everyday life, I won’t be so preoccupied with the subject and I’ll start writing about other things. I promise.
But not today, because I’ve embarked on a new occupational adventure: working two jobs at once.
First, a little background. When I started my temporary job at the healthcare company on March 10, I was asked what my shift preference was, and I said it didn’t matter. So they put me on the night shift, 5:30 to 10:30 p.m. The reason was simple: the company’s office space was maxed out in the daytime, but they could bring in more people at night and put them in the cubicles vacated by the day crew at 5:00. As turnover created vacancies on the day shift, night people would be moved to the day. That’s what happened in my case; after a couple of weeks of working nights, I switched to daytime.
We temporary employees were hired to help the company meet a major deadline at the end of May, and it was made clear that our employment would end as of June 1. (I had no problem with that — a temporary job is much better than no job, and it gave me more time to find something less temporary.) Now, normally, when you are offered a new job, you have to quit the old one. But it occurred to me that in this case, I could overlap them. I could ask to be moved back to the night shift, and keep my temporary job until the end of May as originally planned. Was I insane to consider this? Perhaps, but I decided to do it for two reasons. First, my temporary employer had done me a big favor by hiring me when I badly needed the work, and I didn’t want to repay their kindness by leaving them shorthanded when they needed me. And second, my family can really use the extra money.
So now I work at IBM during the day, and when 5:00 comes, I drive to my other office and work until 10:30. This means that except on weekends, I’m always at work, in my car, or sleeping. I could never adopt a lifestyle like this on an ongoing basis, but I only have to endure it for a month. How hard can it be? Performing in Cinderella last fall was pretty grueling too, with rehearsals and performances almost every day for about six weeks. I got through that experience OK, and I think I can survive this one too.
My phone may have stopped ringing, but the demand for my services continues to outstrip the supply. I’m overemployed!

Apr 30

Getting started

My first day as an IBM employee was April 30, 2001: two years ago today. It’s nice of IBM to commemorate the occasion by bringing me back as a contractor, even if they did miss the correct date slightly. Actually, April 30 was the first day of a two-day orientation class for new employees. My employment did commence on that day, but I did no work whatsoever until May 2. For that matter, I probably spent the rest of my first week obtaining the logins and passwords I would need, getting a phone and a computer installed, and attending various meetings. Which is what I’m doing now, too.
It’s amusing that IBM thought I needed two days of instruction on how to work there, since at that point I already had about four years of experience writing IBM manuals. I started doing that in 1987, when I was an employee of a documentation services vendor that had IBM as its major client. I wasn’t an IBM employee and I didn’t work at IBM, but 100% of my time was spent developing IBM manuals with IBM tools. (In fact, I would go into our computer lab, sit down at a terminal, and log on to one of IBM’s mainframes to do my work. I was “working remotely” before it was cool.) When I left that job in 1988, it was to accept an offer to go out to IBM’s main site in Research Triangle Park and work as a contractor — not employed by IBM, but sitting in an IBM office and using IBM tools to document IBM products. I did about three years of that, in 1988-89 and 1991-92.
So by the time I became an actual IBM employee in 2001, I had already “started work” as a developer of IBM manuals several times. And on none of these occasions did anyone spend two days explaining my job to me. They basically showed me where to sit, gave me some books to read, and left me to figure it out on my own. Which was just fine with me; I learn faster if I can move at my own pace, skip the stuff I already know, and don’t have to listen patiently while other newbies ask dumb questions. Now I’m back as a contractor once again, which means no orientation class. What a relief! If I ever do manage to return to IBM as a direct employee, I hope they won’t make me sit through two days of handholding again. Honestly, folks, I do remember how to do this job.
But Human Resources bureaucrats move in mysterious ways. Before I could start this latest contract job, IBM required my contract agency to hire a security firm to run a background check on me. Of course IBM ran a background check of its own before hiring me two years ago, but I guess they had to be sure I hadn’t committed any new felonies since they laid me off last June.
It seems appropriate that Building 002 — where I went yesterday to have my badge made — has a revolving door. If IBM didn’t have one of those, they would need to install it just for me.

Apr 29

Return

June 21 of last year was my final day as an IBM employee. Before departing, I wrote these words on my office whiteboard:
I’LL BE BACK. — A. Schwarzenegger
It took me a while to fulfill that promise, but today I am back at IBM as a contractor. In fact, I’m posting this from my new office. Said office is not where I thought it would be — although my interview took place in Research Triangle Park, it turns out that I will be working at IBM’s site on Six Forks Road in northern Raleigh. I didn’t even know IBM had a site here. But if this is where Big Blue wants me, then so be it.
As is typical on the first day of a new job, not everything was ready for me when I arrived. For example, my phone has still not been turned on. (I have my mobile phone in my pocket, though, so I’m not exactly incommunicado.) However, my e-mail account was activated a couple of days ago. When I accessed my inbox for the first time, I found that I had a half dozen routine messages about things like passwords and voicemail access. I also had twenty-nine spam messages.
UPDATE: Number thirty arrived while I was posting this entry.

Apr 19

Income tax strategies

Matt has a point , but I think his analysis is somewhat simplistic.

Sure, simply being chronically unemployed will dramatically reduce your income taxes. But it also leaves you without any money! The trick is to become unemployed at just the right moment, so that you end up with a bunch of money when you can really use it. Here is the strategy I used:

  1. Be gainfully employed for the first half of the year, earning lots of money and paying taxes at a breathtaking rate (based on what the government thinks you’ll earn over the entire year).
  2. Lose your job in June and don’t work again for the rest of the year, slashing your annual income in half and placing yourself in a much lower tax bracket.
  3. The following April, file your tax return, collect a large refund from the government, and deposit it in your bank account.
  4. On your way home from the bank, stop off at your auto mechanic’s shop to ask him why the words SERVICE ENGINE SOON have appeared in glowing letters on your dashboard.
  5. After the mechanic finishes replacing your transmission, write him a check for all the money you got back from the government and drive home.

See what you can accomplish with a little planning and strategic forethought?

Apr 18

Yes!

They didn’t keep me waiting. The recruiter who arranged yesterday’s interview called today and said, “Would you like a job?” Apparently the folks I met with at IBM yesterday really are eager to bring in a new technical writer. In fact, they want me to start on the 28th — that’s a week from Monday. I accepted, of course.
The recruiter relayed something the IBM folks told him. They said that I was “far and away the best candidate” they had interviewed for the job, not just in terms of experience and skills, but also in terms of personality fit. They think I’m highly compatible with their team and their style of doing things. As it happens, that’s exactly the way I see it. IBM is my favorite place to work. I’ve known since the first time I set foot on an IBM campus, fifteen years ago, that the company and I were made for each other. And while it’s hard to judge on the basis of half an hour of conversation, I liked the people I met yesterday and felt that I would enjoy working with them. Evidently it was mutual.
It may seem that I’m boasting here, but consider the context. Being told that I’m the best candidate comes at the end of ten months of the opposite: having prospective employers tell me that I’m not the best candidate, or (in most cases) that I’m not a candidate worth interviewing at all. After that experience, I think I’m entitled to savor my victory.
(Of course, while you’re considering the context, it may occur to you that if these IBMers are in such a hurry, they can’t have interviewed all that many candidates. Being “far and away the best” is not as big a deal if they only talked to a total of, say, three people. But if that’s what you’re thinking, I don’t want to hear it!)

Apr 17

Another visit to IBM

Today’s interview went quite well, I think. It turned out to be a sort of combined interview for Managers G and H. As I understand it, the contractor they plan to hire will be a shared resource, doing work for both groups. When I got to IBM, I met first with Manager H and two members of her team. After chatting with them for about half an hour, I was ushered into another office to talk with a member of Manager G’s team. (G himself was offsite today.) They seemed to like what I had to say, and indicated that they would be making a decision quickly. This is consistent with what I was told later by the recruiter who set up the interview — they are in a hurry to fill the opening and will probably make a decision in the next few days. So at least I won’t have to wait long for a response.
Not that I’ll be sitting by the phone, biting my nails. Friday is officially a holiday at Perigee, but those employees who would like to earn extra money are welcome to work on Friday and Saturday, so I plan to do so.

Apr 16

Alphabet soup

It’s not over yet. I got two calls from recruiters on Tuesday, both related to IBM contracts. One was a follow-up from the agency trying to fill Manager G’s opening; they’re submitting my resume. The other call, from a different agency, was to arrange an interview with Manager H, another one I’ve never heard of before. I’ll be meeting with him tomorrow.
UPDATE: Make that “meeting with her.” I was mixed up about exactly who Manager H was.