Employment is a good thing

Oh, by the way…starting Tuesday, I’m working again.

Actually, I’ll be working tomorrow, too, on a one-day assignment from my temp agency. But Tuesday I start training for my new position.

It’s nothing overly glamourous — no dream job, no mind-bogglingly cool opportunities were dropped into my lap during my week of notoriety — but it’s a good steady job, which I’m quite satisfied with. I don’t want to get into too many details (for hopefully obvious reasons), but it’s another quick-print shop, running copiers, dealing with customers, etc. It will do quite nicely for the foreseeable future as I continue to work on getting enough bills paid to be able to investigate loans and grants to get me back into school, which I hope to accomplish in the coming year or so.

In any case, the main thing is that I only had to deal with two weeks of stressing about unemployment. I’m making a bit less than I was before, but not so much so that I have to worry overly much. I just won’t be able to splurge on another new computer anytime soon. ;)

Thanks again to everyone who provided support, through comments, e-mails, messages, phone calls, and everything else.

What the hell's on my doorknob?

Doorknob goo

I’d just finished getting dressed to head out to the club, when I walked out the door and reached behind me to swing the door shut. When I grabbed the handle, though, something seemed wrong — it felt slick. Odd. I turned to see if there was actually something there or if I was just fooling myself, and found…well, I don’t know what.

The entire doorplate on my door has been covered in some sort of slick goo that I can’t identify, enough so that the goo has dripped down the front of my door. There’s a slightly sweet smell that I can’t identify to the goo, and it appears to be eating through the paint on the door.

Needless to say, the first thing I did was get back into my apartment and wash my hands. I didn’t want whatever it was to be on my skin any longer than absolutely necessary. After that, I went back out and checked the rest of the doors on my floor to see if any of them had this same thing happening.

Nope. Just my door.

It eats away at the paint

Needless to say, this has got me somewhat freaked out. And, of course, there’s nobody I can call or ask about it, as it’s 11pm on a Friday night. Hardly office hours.

Is it just a prank of some sort? Or something more serious? Am I being targeted directly for some reason? It’s possible — with my resumé online, my address is now public knowledge, and I’ve discussed my DVD collection, my computers, my CDs, and who knows what all else online in the past. It’s at least theoretically possible that someone could have tried — or be planning to try — to get into my apartment while I’m away.

I have no idea what to do now. I’ve taken these photos, but I’m not sure if this is enough to make a call to the police. I don’t really want to leave, just in case it is someone planning on entering my apartment while I’m gone.

This sucks. And I’m freaked.

Grrrr.

Fun with piercings

Body piercing is something I’ve never been terribly interested in, on a personal level. I have no problem with it on other people, and often find it quite attractive, I just have never felt any need nor desire to do it to myself. For quite a few years, I used to joke that I was a “freak among freaks”, as I was the only one in my group of friends who was “unmodified” — no piercings, no tattoos, no body modification of any sort. Once I got my tattoo that was less true, but I’d still joke about it from time to time.

One night, the club I was DJ’ing at had just closed down, and our group of late night rabble rousers had found our way over to our usual post-club breakfast spot, “Vinyl” (Village Inn, Northern Lights — VINL). Most of the wait staff there had gotten used to us, generally we were liked, or at least tolerated. A bit rowdy, to be sure, all amped up on sugar and caffeine, but as the club was a non-alcoholic all-ages dance club, at least we weren’t drunk and rowdy.

We were being especially energetic this night, and at some point when the waitress came by, one of us apologized to her for being so raucous. “Oh, don’t even worry about it,” she assured us. “You’re not that bad, and besides — working the bar rush shift, I don’t think there’s anything that’ll surprise me anymore.”

Oooh — a challenge! Marc and I looked at each other. To this day, I have no idea where the inspiration came from, as I don’t remember us discussing this in the least. One way or another, though, our Muse was with us.

“Excuse me — miss?”

“Yes?”

“I bet we could surprise you.”

“Oh, really?”

“Yup. Tell you what. If we can come up with something you’ve never seen before — that won’t get us kicked out or arrested — we get our breakfast for free, okay?”

She laughed. “All of you?”

“No, no — just us two,” I said, pointing to Marc and myself.

“Well…what’cha got?”

We grinned. I grabbed the Dr. Pepper she had just brought me and set it between us, and Marc took the straw and placed it in front of him on the table. Sticking out his tongue, he calmly unscrewed the ball of his tongue stud, dropped it in the empty coffee creamer dish, then slid the post out and put it in the dish. He then unwrapped the straw, brought it up to his face, and slid the straw into the hole in his tongue until his tongue was halfway along the length of the straw.

“Okay,” said the waitress. “The straw is a little freaky, but I’ve seen people play with their tongue piercings before.”

“No worries,” I said.

Marc then leaned over, letting the bottom end of the straw drop down into my Dr. Pepper. I leaned over, took the top of the straw in my mouth, and proceeded to take a few big sips of my Dr. Pepper, though the straw, right through Marc’s tongue.

We got our breakfast for free.

(Inspired by Nate‘s Household Items I can fit in my Piercings post)

Puts me to sleep every time

Early fall, 1997.

James, Richard and I had just gotten out of a late showing of that year’s Sci-Fi/Horror film, “Event Horizon“. None of us had known quite what we were in for when we decided to go, aside from the most basic premise of “something creepy happens in space,” but it looked fun, so off we were.

We had a blast. The movie itself, if you haven’t seen it, is either really good or really horrible, depending on how you look at it. As a horror movie, it’s pretty good — as a science-fiction movie, it’s horrendous. That night, though, we just had a lot of fun with the horror movie part, sitting in the dark in a huge theater, jumping at all the cheap thrills and loud noises, and thoroughly enjoying it.

Leaving the theater sometime after midnight, we were so jazzed on adrenaline that we were bouncing off the walls, so we stopped off at the local grocery store for some snacks.

“I like it here,” commented James as we walked down the aisles. “It’s warm…the lights are on…there’s air…. Can we stay?”

We got to the checkout counter, and I started skimming the tabloid headlines as James and Richard paid for their goodies. “Hey guys,” I said, and held up the latest Weekly World News. “Alien’s Last Words!”

James just looked at me and deadpanned, “Ack. Ack ack. Ack ack ack ack. Ack.”

Eventually we headed back to my apartment. Once we got there, James decided that he was still too amped from the movie to have any chance of going to sleep. In order to relax and calm down, he decided the best thing to do would be to watch a nice, calm, relaxing movie.

Like Aliens.

True to form, he was asleep before the movie ended.

So close…

…but not close enough. My temp agency and I spent the morning getting me set up with an assignment with a software company’s call center. Everything was looking good (including running me through some quick tests that verified my typing speed at 80 WPM, and a combination listening/data entry test that I apparently scored around double the average score on), they handed me the address of the call center, and I headed back home to wait for the confirmation call.

Once I got home, I hit the Seattle Metro Online Trip Planner to figure out how to get to the call center — and realized that it was about a two-hour commute that involved a one mile walk. Wow. Much as I need to find another job, that’s a bit much, so I had to call back and let them know that, much to my chagrin, I had to turn down the assignment. Bummer.

Back to square one…

This just hasn't been my best week

Earlier this week, I discovered that my site design had been appropriated without acknowledgment or credit by a third party. Upset about this, I posted about it. Some of my readers were able to provide me with an e-mail for the likely party, and I e-mailed them. I also cc:’d an administrator at the school.

While this action resulted in the site being first removed and then redesigned, it has been pointed out to me in the comment thread to that post that I managed to do this person essentially just what had just been done to me — a mistake that could have easily been taken care of quickly and quietly became more public than had ever been expected or desired.

What can I say — they’re right. I shouldn’t have been so quick to take the actions that I did. Already overstressed and overwhelmed from the attention my site has been getting of late, I reacted too quickly and without enough thought.

The following is the latest in a series of e-mail messages I have been trading with the person in question, expressing my apologies to him.

Thank you very much for accepting my mistake, please notify me of the appropriate amount of money I should paypal to you in order to repay you for bandwidth my site took by using an image served from your server.

Don’t worry about that — chances are it wasn’t terribly much, and as I’ve been getting an insane amount of traffic lately due to my recent experiences with Microsoft, my bandwidth limits are so ridiculously shot at this point that any traffic you might have added would be just a drop in the bucket.

It has been pointed out in the comment thread for my post that I may have jumped the gun in cc:’ing your academy superiors in my initial e-mail without first seeing if you would remove the site on your own. In retrospect, I should have given you the chance to remove it on your own — the only defense that I can give is that as there was no current e-mail address listed when I found your site, I was not certain I was contacting the right person, and at the time I found your site, I was somewhat overwhelmed from the attention my site had been getting and was somewhat touchier than I usually strive to be.

In my experiences with Microsoft (detailed earlier on my website, though it’s entirely possible that that is how you found my site in the first place), I made a mistake, and was immediately given the most extreme punishment possible. I then turned around and essentially did the same to you. For that, I most certainly owe you an apology as well.

I do hope that this hasn’t caused any major problems for you at the Academy (and as such, will also be cc:’ing this apology to the same contact person at the Academy that I did my initial e-mail). We’ve each recently made mistakes that have become more public than we expected or would have wanted them to. Hopefully each of us can learn from this in the future.

Again, good luck to you, and best wishes.

Everybody makes mistakes. Of late, I’ve been making my mistakes loudly and publicly — not something I’d really recommend to anyone. ;) Hopefully I can stop this trend before it gets any worse!

One last interview

I think that this should be the last of my posts regarding my recent notoriety. Tech news site BetaNews interviewed me about the entire affair yesterday, and the interview has just been posted on their site.

On October 23, Michael “Woody” Hanscom posted a picture to his Web blog, intended to garner a chuckle or two from a few close friends and colleagues.

>

The reaction the picture drew from his employer can only be compared to a kind of Orwellian nightmare where anything an individual does online can come back to haunt them. That nightmare is the reality faced by an increasingly vulnerable corporate world where the Web can be used as a tool to disclose potentially sensitive and damaging trade secrets to the masses.

Thanks to David Worthington for conducting the interview.

Fifteen minutes of fame

#1 and #2 on Blogdex!

Wow. The past day has been absolutely incredible — naïve as it may seem, I really didn’t expect all of this response to come from my little adventure.

While I had to give up on linking back to every site that linked to my post simply because there were too many of them to keep track of, some of the biggest so far have been MetaFilter, The Register, and Slashdot. Crazy. I’ve also had interviews today with both MSNBC (ironic, no?) and the Seattle P-I — I’ll post links to those articles when they become available.

Seattle PI Front Page, 10/30/03

Update: The article in the Seattle P-I is now online (and it’s on the front page of the print edition — yikes!).

Update 2: The MSNBC article is also online.

Following up on some of the many comments that have been left on my site and others where this has been mentioned:

Yes — I made a mistake

This has been pointed out many times, sometimes more politely than others. My posting of a photo taken at the Microsoft campus was (most likely) a breach of contract. The only reason I qualify that with “most likely” is that, due to my particular employment situation (a temp worker contracted to a vendor who had an account at Microsoft), I never went through any Microsoft-specific orientation or “rules and regulations” session, so I can’t say for certain that there is a “no cameras” clause as a condition of working at or for Microsoft.

No cameras?

Now, even without knowing about a “no cameras” clause, common sense does come into play here. Had I been foolish enough to take pictures inside any of Microsoft’s buildings, of the buildings themselves, of the offices of any of the employees, or anything similar, than I would fully expect to be terminated. As I mentioned in my Of blogging and unemployment post, I thought that the picture was taken in such a way that it would not cause any issues, revealing only an unmarked truck with some computers, and a small section of loading dock that could be nearly any loading dock on any building across America.

In fact, it may very well be that the picture itself is not what caused Microsoft to decide that I was no longer welcome on their campus. Again, as I mentioned in the ‘Of blogging and unemployment’ post, it appears that it was the combination of the picture with the information about what building I was at when I took the picture that prompted them to make the decision that they did.

NDAs (Non-Disclosure Agreements)

Many people have posited that my ultimate downfall was a breach of an NDA. This may or may not be the case. Again, because of the circumstances of my position at Microsoft, I never signed a Microsoft-specific NDA — however, this does not mean that I was not bound by an NDA. I would not be at all surprised if there were some form of NDA clause as part of the contract between Microsoft and their vendors. Now, I’m not sure if my post, the picture, or the combination of the two would constitute a breach of any NDA clause that I may have been bound to. I didn’t think so when I made the post, however given recent events, that may very well have been where I was wrong.

Who’s to blame?

In the end — me. I really don’t blame Microsoft for their actions. By my best guess, they saw me as breaking the rules — whether those rules were a “no cameras” clause, an NDA, or something entirely different — and decided that rather than give me a second chance and run the risk of me doing something similar in the future, it would be better to just cut me loose before I could do any more damage.

I can (and would) swear up and down that I would never divulge any internal Microsoft information. Heck, during my tenure at the printshop, I saw a lot of information that would have gotten me fired faster than this did if I’d been so foolish as to publish it. As “evil” as Microsoft may be popularly perceived, I don’t think it’s any secret that they have many incredibly intelligent people working for them, who come up with some truly astounding ideas. I’ve seen advertising campaigns in their preplanning stages weeks before they hit the press, I’ve seen internal documentation on programs that are still in development, and I’ve seen ideas and technologies that I would love to have available on my Mac at home. None of those have ever been mentioned here in my weblog, and even now, this is the most I intend to say about them.

However — while I may not have seen my post as violating Microsoft’s security standards, someone there did. Because of that, they may feel that it’s not worth the risk of continuing to allow me access to proprietary information that I could, in theory, leak to the world.

I may not like the way that they handled this. While I didn’t plan for my post to generate the amount of attention that it’s received, it has, and now Microsoft is facing a certain amount of bad press because of that. It may have been far better for them (on a PR level) to reprimand me and have me take the post down. However, I cannot fault them for making the decision that they did, however much I wish that that they had made a different decision.

I goofed. I regret it, but the damage is done. Mea culpa, mea culpa, mea maxima culpa. ;)

Future employment

I’ve seen a lot of comments suggesting that I apply to Apple — even some stating that Apple should just give me a job. As amusing as this idea is, I have to say that even I find it entirely unrealistic.

First off, as some have pointed out, my post could be seen as indicating that I have a propensity for disclosing internal company information. That’s not likely to put me very high on the list of prospective candidates for any business, let alone one run as tightly as Apple.

More importantly, though, is the simple fact that as my resumé shows, I’m woefully under-qualified for many computer-based positions. I don’t have a college degree. I don’t have any sort of computer certification. Aside from the past eight months, I haven’t even held a position that was primarily computer based. Instead, I’ve spent ten years working in the quick-print industry, running high-end digital copiers.

This isn’t to say that I’m a computer illiterate, of course. I’ve been a fairly typical “computer geek” for most of my life. I have experience with a wide range of systems, starting with CP/M on an Osborne 1, a few different flavors of *nix, DOS and Windows based PCs, and my primary focus, Apple Macintosh computers. I like learning about how all of the bits and pieces work, and how they work together. I’ve been fascinated with HTML for years — my first website went up in 1995, and I’ve been “blogging” in one form or another since 1998 or 1999, though I only have archives dating back to November of 2000 — and while I may not be much of a designer, if I may toot my own horn for just a moment, I think that my HTML code is damn good. I’ve spent a little time mucking around with Perl, Java, and Javascript, not enough to be a programmer (by any stretch of the imagination), but enough that I can take a look at the code and at least get a general feel for what it’s doing.

All of this, though, is self-taught. And self-taught doesn’t really get you jack, for the most part, especially when it doesn’t show on your resumé. My biggest regret with all of this is that, as my position for the past eight months has been working in a prepress environment, getting digital files print ready, I was finally getting some resumé experience that could show that I really did know something about computers. Now, however, I’ve lost that position, and I’ll just have to hope that if I’m lucky, those eight months might be enough for someone to give me a chance again at some point.

In the end, it all comes down to hitting the streets, throwing my resumé around town, and seeing what comes up — and hoping that when an interviewer googles my name, all this brouhaha doesn’t scare them off!

Rent (or “Wow — you all rock.”)

While I’m sure after reading the article at The Register that many people will find this hard to believe, I originally only mentioned financial matters because I had had enough people inquire that it was easier to do it in a single post than e-mail everyone. I’ve never expected donations in the past, and I wasn’t expecting donations this time.

Quite honestly, I’m floored.

An incredible number of people have tossed a few dollars my way, and I really don’t know how to thank you all. It’s enough to ensure that my rent for the month is taken care of without having to hit my emergency stash, and just a little over (which will go for good cheap eats — like Top Ramen, the bachelor’s/college student’s/first-time-apartment-dweller’s food of choice!). Many, many thanks, karma points, and mojo out to all of you. You rock.

Surviving Slashdotting (or, “Commercial time!”)

Lastly, but definitely not least, I’ve had quite a few people inquire about the weblog itself — specifically, who hosts it, and how it’s managed to stand up to the abuse of a Slashdotting as well as it has.

My site is hosted by TypePad, from the same good people that produce MovableType. I used MovableType for quite a few years on a personal server running out of my apartment (thank goodness I’m not using that setup now — my poor lil’ G3 webserver would be in puddles on the floor by now!), moved to TypePad when I got the invitation to be part of their public beta test — and have stuck with it since.

As I’m a confessed HTML geek, I find TypePad’s pro level perfect for me. They take care of all the niggling little details of server management, and I still have full control over all the HTML code produced by the system. I can be as picky (ahem…anal) as I want about the code that my site produces, and I do what I can to ensure that the pages are as clean as possible — minimal graphics, standards compliant code that’s easy to read if someone should dive into the source, CSS for presentation, and all the rest of the current buzzword goodies.

I can’t recommend TypePad enough — or MovableType, if you prefer to handle the server end of things yourself. I’m also very grateful to them for handling my Slashdotting (their first, apparently!) with such aplomb. As far as I know, there were very few glitches over the course of the day.

Conclusion

So what have I learned from all of this? Well, firstly, and most importantly — keep my big fat mouth shut! ;)

Some people have made comments along the lines of, “this is why I blog anonymously.” I have to say, that I don’t honestly think that that’s necessarily a perfect solution. Given the well-known power of Google, it’s very easy for me to believe that many anonymous blogs are — or at least could be — far less anonymous than their authors might believe. A comment here, a phrase there, a certain choice of words, and suddenly, someone’s put the pieces together (“They said that their birthday was on or around this date, they got together with this group of friends here, they took a trip to Disneyland here…”) and they are suddenly “outed”.

I made the conscious choice a few months back not to blog anonymously. Prompted by a post by Anil Dash, I decided that given the All-Seeing Eye of Google, I would rather do what I could to “own” my own name. I stopped using my prior online pseudonym of ‘djwudi’, began using my given name of Michael Hanscom whenever leaving comments on sites, and registered the www.michaelhanscom.com domain name. To me, the ability to have some amount of control in ensuring that information that is connected to my name is actually connected to me is worth the risk of situations like what I just went through.

Basically, it all boils down to making sure that you know just what your employer would or would not be comfortable with you mentioning on your weblog — and if there’s any doubt, don’t mention it. I didn’t, and it got me canned. You shouldn’t let the same thing happen to you.

Thanks much for all the attention, comments, and food for thought over the past few days. It’s been a bit overwhelming, but one hell of a ride.

Thank you!

First things first — many, many thanks to the many people who have passed on words of encouragement to me in my time of trial. With a normal readership of about ten people that I know of, I wasn’t expecting to get much response beyond my family and a few friends. The ‘net being what it is, though, tales of my trials and tribulations seem to be spreading, and I’ve gotten many nice comments, e-mails, and phone calls, not to mention links on a growing number of sites.

Mentions that I’ve found as of 10/29/03 @ 0234:

I’ve spent part of the day updating my resumé (a task that I have to admit I always dread), and have polished it up to the best of my ability and posted it here. With any luck, between the temp agency, my own efforts, and what little notoriety I may gain in my fifteen minutes of fame, this stretch of unemployment won’t last too long. In any case, I’m certainly keeping my fingers crossed (though it does make it a bit harder to type, I can use all the luck I can get right now).

To address some of the concerns and questions I’ve received:

Legal recourses

A couple people have inquired about possible legal recourses. This is an avenue that I don’t particularly want to investigate, for a few reasons. First, I don’t think that the time and trouble is worth it, and second, I’d be willing to bet that somewhere in the labyrinthine red tape of contracts among my temp agency, the vendor, and Microsoft, this situation is probably covered in one form or another.

In the end, what it boils down to was a slight misjudgment on my part. While I (and many other people) may find Microsoft’s reaction to be extreme and unnecessary, chances are they had every legal right to make the decision that they did. I would certainly have preferred that they simply request that I take the offending post down (which I would have done in a heartbeat), but for whatever reasons, they chose not to take that route.

Future plans and possibilities

Thankfully, this appears to be solely an issue between Microsoft and myself. While I got the news from my supervisor, it was made clear to me that there was nothing he could do about the situation, and he was sorry to see me go. As I’d been a valuable member of the team in the print shop, able to cover nearly any position outside of administrative duties, losing me will be a bit of a blow to the shop (now, I’m not so amazingly egotistical to claim that the place is going to go down in flames just because lil’ ol’ me isn’t chipping in anymore, mind you — I just know that I was able to help out wherever I was needed, and I enjoyed doing it).

Seeing as how he was also caught off guard by this situation, he’s said that he’ll ask around and see if there might be any other open positions outside of Microsoft that I might be able to be shuffled into. This is no guarantee, of course, but it’s certainly nice to know that he thought highly enough of me to at least take a few minutes to ask around about possibilities.

I’ve also received a couple of requests for my resumé via e-mail, which have been sent out to everyone who asked for them.

In the end, though, I’m still crossing my fingers, waiting to see what may come down the pike.

Finances

A few people have inquired about how I’m doing financially. I have to admit — things are a little dicey here. Rent is due in a week, and while I’ll be able to dip into some emergency money to get me through this round, I will need to have stable income by the time November 5th rolls around or I’ll be in very dire straits. It’s quite typical, in a Murphy’s Law kind of way, that this would happen just a few weeks after I blew my savings on a new computer. Ah, well — there was certainly no way to plan for it.

Now, I’ve never been much of one for asking for money — I’m quite stubborn by nature (according to my parents, one of my first words as a child was “self!”), and generally, if I can’t handle something on my own, well, that’s just the way it goes. Besides, I can more easily see a website/weblog requesting donations when they focus on a specific topic, rather than being the essentially random collection of technical babble, political indignation, personal musings, and occasional bad humor that this site tends towards. ;)

That said, however…(oh, sure, first the disclaimers, then the heart rending plea for help, complete with a John Williams score — oh, can I get Steven Spielberg to direct the TV spot?)…I have had a PayPal donation button in my about page for months now, as well as the Amazon links at the bottom of each page. To date, these have netted me all of — hold on, let me check — approximately $12 from my Amazon Associates account, and absolutely nothing from the PayPal button.

Now, that’s about exactly what I’d expect to see, and I certainly don’t expect it to change. Heck, with the economy the way it is, there’s not a lot of people out there who have the spare change to help support some anonymous bloke whose sob story they just stumbled into while wandering around the ‘net. But — and there’s always a but, isn’t there? — should anyone feel moved to make small donation, whether through the PayPal link or by using the Amazon banner on my site to go shopping, I certainly wouldn’t complain in the least.

And I believe that brings us up to date. Once again, thanks to all of you for the kind words. Often, those are worth far more to me than anything else.