Today's adventure: trying to figure out how to get two rather large pallets of networking equipment from the curb to the NOC. Without a pallet jack.
But hey, at least it was only 99 degrees out.
Today's adventure: trying to figure out how to get two rather large pallets of networking equipment from the curb to the NOC. Without a pallet jack.
But hey, at least it was only 99 degrees out.
Dear everybody who has ever mailed me back a filthy keyboard,
I don't mail you my garbage for you to throw away.
Maybe someday I'll just mail a user a half-eaten sandwich. Here, have some disgusting trash.
You know, I spend a lot of time complaining about stupid users. So let me take a moment to thank the smart ones.
If you have ever packed something appropriately, so that it's properly cushioned and doesn't bounce around, thank you.
If you have gotten it in the mail as soon as it was ready to go so that I didn't have to call and remind you, thank you.
If you made sure that all your stuff was properly backed up so that I didn't have to dig your computer out of a stack weeks later, thank you!
If you haven't shipped a horrific, toxic-looking keyboard back for me to dispose of for you, seriously, thank you so much.
And if you've actually thought to wipe down your equipment before shipping it back, I could kiss you.
Really. I got an old computer back today that somebody actually took a minute to clean first and it legitimately made my day.
It's vexed me for years and years that end users seem unable to comprehend very simple things like what a Web browser is, the difference between Windows and Office, and how to come up with effective search terms to type into Google.
In more recent years, I have come to understand that, for some of these people, simply putting a thing in a box and affixing a label to it is a nigh-impossible process.
Today I received a desktop computer that was just thrown into a box with no padding whatsoever -- a current model and redeployable (well, maybe not anymore) -- and an old, past-end-of-life laptop packed inside of multiple boxes and wrapped in layer after layer of bubble wrap with tape. The former shipped from out-of-state, while the latter came from an office two blocks away from mine. Would be nice if they could work out some sort of happy medium.
Two weeks ago I missed a day of work with a migraine. The day after that I scrambled and played catchup and shipped two days' worth of computers in one day. Turnaround time from shipping a new computer to receiving the old one is right about two weeks, so today I was hit with two days' worth of returns in one day.
And okay, I've spent enough of this post complaining about stupid users that I'll take a moment and acknowledge my own stupid fuckup of the day.
I had a giant pile of boxes in front of me and a small pile of outbound machines, and I started to stress out about it a little. And I made a mistake.
I took a break from processing returns to ship a machine out, and I got my wires crossed and started going through the return process. I deleted a user's old computer and its access group from ActiveDirectory, before shipping her replacement. And since I don't have access to fix that, I had to ask my coworker to take care of it.
It's about that time I decided I should probably take some deep breaths and try to relax before doing anything else -- not just for fear of more sloppy mistakes, but because if I'm not careful I'll give myself another migraine, and then I'll just be going through this same song and dance again in a couple weeks.
Still opted not to take a break right away -- because that just means more crap I gotta do tomorrow -- but I slowed down a bit. Got through maybe half the stack, finally got enough facefuls of dust from old Dells that I decided to call it quits for the day.
So, more to do tomorrow. But I guess that's the closest thing a temp ever gets to job security.
...do you think maybe "You may be a victim of software counterfeiting" is just a bit of a heavyhanded way of saying "Couldn't connect to the authentication server"?
Had a spot of trouble with a hard drive at work today and decided to see what thumb drive Linux is like these days. I found a program called YUMI (Your Universal Multiboot Installer) at pendrivelinux.com and discovered that it's pretty great.
YUMI is a simple Windows executable. It's got a long list of Linuxes -- Ubuntus, Fedoras, server OS's like CentOS, small OS's like Damn Small Linux and Puppy, and non-Linuxes like FreeDOS, as well as special-purpose diagnostic software like Ultimate Boot CD and various AV vendors' recovery discs.
Click on one of the supported OS's, point YUMI at an ISO, and it'll install it on your thumb drive -- as many as will fit, with GRUB to select which one you want at boot time. Better still, if you don't have an ISO, it's got a one-click download for every single one of them.
And while it's got dozens of supported OS's built in, it'll do arbitrary bootable ISO's, too; I tried two and found that one (the latest FreeDOS installer) worked while the other (Hitachi Drive Fitness Test) did not.
As for Puppy, it's definitely seen some progress in the years since I last used it but my gripes remain much the same: instead of programs being labeled by name, they have generic descriptions (hypothetically a good idea for neophyte users who don't know what Seamonkey is, but in practice I think "Web" would probably be a better name than "Browse"), and the package management system is less than entirely intuitive. Still, for coming in around 100MB it's a damned impressive, and a whole lot easier on the eyes than the last time I tried it.
Anyway, YUMI's made it easy enough to set up that you can easily spend a couple hours (or more) screwing around with various USB bootkits. It's an impressive piece of software and one I'll definitely be keeping in my admin toolkit.
(There appears to be a Linux equivalent called Multisystem LiveUSB Tool. I haven't tried it out yet so I can't vouch for it, but if you're looking for, you know, a Linux tool for Linux, that might be something to check out.)
Stayed home from work today with a migraine. One of the worst of my damn life -- no nausea with this one, fortunately, at least, not at first, but just this awful skull-crushing agony as if a thousand Thetans were pounding at the inside of my skull trying to ec-scape.
Woke me up at about 3:15 AM, too, which to the best of my recollection is a first. I've often woken up in the morning with a migraine, but seldom in the middle of the night. I was covered in sweat, too; don't know if that's some new and exciting feature of the migraine, or if I was running a fever, or just because I live in Tempe, Arizona and it is June and our lows are around 80 degrees this time of year.
Got up at 6, called in, popped a prescription migraine pill (with codeine!), and went back to bed for a fitful in-and-out-of-consciousness "sleep" until about 11 AM.
(Tangentially: I had a job, a couple of years ago, where some middle-management fuckwit had the bright idea of combining the sick line with the help desk. One day I called in and, hours later, got a call from work asking where the hell I was -- I explained that I'd called in, but apparently the help desk hadn't gotten around to my ticket yet. I came in the next day to discover that my ticket had finally been submitted at 4:45 PM, which, as you might suppose, is not the optimal time to let an office know that a worker will not be coming in today. Like, I think by 4:45, they've probably worked that out.
Best of all, I was then randomly selected to fill out a survey about how satisfied I was with my interaction with the help desk.
I made a point of not raking the tech over the coals -- I noted that help desk techs have a lot on their plate and often poor mechanisms for prioritizing their tickets; if you've ever worked help desk I don't need to tell you that nobody ever submits a ticket as low- or medium-priority -- and said that trying to combine the sick line with the help desk line was a fundamentally bad idea.)
Anyway. Ate some instant ramen, washed another codeine down with a few cups of coffee, and that managed to knock the headache down from "I can barely move" to "dull, ever-present throbbing". And I don't know if it was the codeine, the caffeine, or the pain, but by this point my coordination was completely shot.
Then I fired up the ol' Nintendo.
There's something I learned, around the age of 12 or 13: playing video games helps with the pain.
My mom and my grandparents didn't really buy that, and I suppose under the circumstances I can't blame them -- I was, after all, saying I had a migraine, and then staying home from school and playing video games all day.
But now there's research backing what I understood intuitively as a child: video games have an anesthetic effect. In recent years there have been studies in distraction therapy suggesting that video games have a real and measurable impact on pain management. (For one example: Applications of virtual reality for pain management in burn-injured patients, via the NIH, 2009. There have been other studies besides.)
I find that quieter games tend to be a bit better. And games that don't have a lot of text, because reading makes my head hurt.
I also tend to gravitate toward the familiar, stuff from when I was a kid -- Super Mario World and the like -- and I suspect there's a "comfort food" aspect to this. Though, on the other hand, SMW requires twitch reflexes, and when my reflexes are scrambled by codeine and caffeine it can be a much more frustrating game -- which doesn't help with pain.
Knowing that, today I started with Xenoblade. It's not too heavy on the text, I'm over-leveled enough that it's pretty low-key and not difficult or frustrating, and it doesn't require much in the way of hand-eye coordination or precise movements. (Well, most of it doesn't. Fuck you, Valak Mountain.)
But what it does have is big, vertigo-inducing vistas. Fuck. I was about three minutes in before I started getting nauseous and had to turn it off. Don't know if that's the migraine or the codeine, but I popped a motion sickness pill and decided to try Super Mario World after all.
I picked up my save from the last time I had a migraine and worked my way through Twin Bridges. So I guess my reflexes weren't completely shot.
Then I had a hot bath.
Now here's a question: what the fuck is up with bathtubs?
The standard American bathtub is a rectangle, and it's, what, four and a half, five feet long? And its deepest point is where your fucking feet go.
Who came up with that shit?
I'm actually kinda curious: were bathtubs designed this way because of the belief that baths are for children and teeny-tiny elfin women, or is it that only children and teeny-tiny elfin women take baths because no average-sized human adult can fucking fit in one comfortably?
Decided not to shave afterward. Still jittery. Just because I have the wherewithal to abandon Yoshi to a tragic fate on my way to Soda Lake doesn't mean I trust myself to run sharp objects across my face.
Anyhow. Guess my point is, "staying home playing video games" isn't always as much fun as it sounds. Sometimes it doesn't mean you're slacking. Sometimes it means you're doing everything you can to deal with excruciating pain.
All things considered I'd much rather have gone to work. Because aside from the "excruciating pain" thing, I don't get sick pay, and I'll spend tomorrow playing catchup.
So it goes, I guess.
Dear Every Single Person Who Has Ever Stuck a Label onto the Outside of a Reusable Shipping Sleeve,
What the fuck is the matter with you?
It's interesting -- those last two posts have actually gotten a couple of people to tell me I should post more. A friend I hadn't talked to in a few months, somebody from the messageboard, and, to my pleasant surprise, a stranger. (Or possibly someone pulling a surprisingly elaborate hoax, which I suppose is still flattering in its own way.)
Partly because of the feedback, I'm going to try and write more here.
I've fucked around on the backend a bit; you've probably noticed posts have tags at the bottom now. I've gone through all the way back to when I first started using blogging software in '06, and tagged all of them. I'm half-tempted to go through the older ones, from when I entered everything by hand, perhaps for no other reason but to tally up how many posts each I've devoted to Mike Allred and Kurt Busiek, but that sounds suspiciously like a lot of work for very little payoff. The reason I switched to blogging software in the first place was because I found myself spending a really inordinate amount of time cutting-and-pasting from one page to another.
Speaking of which, I've also updated the KateStory page, fixed broken links, summarized Book XVIII, and added some new character entries, which is exactly the kind of irritating bookkeeping that drives me to go play Nintendo instead of updating the site. Wonder if it'd be worth it to set up a DB so I don't have to manage every character's list of appearances manually. Then again, we haven't done one of these in nearly two years.
And speaking of old crap that seemed like a good idea at the time, I've renamed the "My Personal Life" category, because that was always a pretty stupid name for "What book I am reading/What game I am playing" but which I kept for a dozen years due to a combination of inertia and mild amusement that I could refer to my categories with the shorthand "Life/Stream".
I've changed it to the more boring but more accurate "Status Updates". That still doesn't seem like a very good name, so if anybody's got a better idea I'm open to suggestions.
I ever tell you why this site is called corporate-sellout.com?
I was chatting with an old friend of mine. Girl I went to high school with; we were in drama together, and I went to my junior prom with her.
By this point we were in college. I was a freshman or a sophomore, thereabouts, and she would have been a year ahead of me.
We were still in touch but pretty testy with each other -- you know that age, where you're out on your own but still kinda stressed-out and pissed-off about everything.
Plus, I was still getting over a bad breakup. With her roommate.
Anyhow, we were talking about our majors. She'd picked creative writing and I pooh-poohed it a bit.
Not because I don't believe in writing, of course. She and I are both storytellers, at heart.
But for other reasons. I thought of college as a means to an end, a financial investment for a financial reward. And, well, I was lucky enough that I really enjoyed something that also was, unlike a creative writing, a lucrative degree. (That'd be CompSci, for those who haven't been keeping score.)
She responded, rather angrily, with "Well, it sounds like I'm studying to be an artist, and you're studying to be a corporate sellout."
It wasn't the worst thing she called me in that conversation (it was followed shortly by "asshole"), but it stuck with me.
Mostly because I make a terrible corporate sellout.
Up to that point in my life, I'd never even worked in private industry; all my work had either been for my family or for the government.
I've worked a few corporate jobs in the years since, but I'm still a bottom-rung IT temp. If I were going to sell out, it would have been for a lot more money than what I'm making.
Funny thing is, last I heard she was doing much the same work I am -- she's probably a bit higher up in the chain, actually, because a few years back she took an entry-level phone support job that I refused.
I can't say I regret refusing that job, because seriously, entry-level phone support sucks and I thank the all-powerful Atheismo every day that I no longer work in a phone bank, but I will say that the job I took instead because I thought it'd pay better and give me more room for advancement was...a miscalculation.
So it goes, I suppose. But I'm still a storyteller at heart.
I enjoy the hell out of writing. And I never really stopped doing it -- I just cut way back on doing it here.
I'm pretty damn prolific over on the forums, and I spend more time arguing with idiots in the ComicsAlliance comments section than I'd care to admit. I think I'm much better off trying to redirect at least some of that effort back this way.
I've probably got a pretty good backlog of standalone posts over at Brontoforumus (and maybe even Pyoko, if I feel like slogging through Wayback pages) that I could just copy-paste up here. I expect I'll do a bit of that, in addition to original posts.
I try not to think about the fact that it's been seven years since I got my CS degree and I haven't put it to use professionally.
I entered the field at the wrong time and in the wrong place. It's rough all over, and the housing bubble hit Arizona disproportionately hard. I've spent the past few years working as a temp and building the odd website on the side.
The first temp gig lasted two years -- ironically, longer than any other job I've had. But I got laid off about a year ago.
There's this kind of paranoia you get. It could happen again any time. And it has absolutely nothing to do with how hard you work or how good a job you do. You could be out on your ass tomorrow, on the whim of some guy you've never met.
I've heard some of the "get a job" rhetoric lately and it's just baffling. A hell of a lot of people would like very much to get a job. I've been either unemployed or underemployed my whole adult life, and that's with a degree that, fifteen years ago, could have gotten me six figures.
Not that I intend this as a pity party. I've got work now, and it pays well enough to live comfortably while still squirreling away enough each week that I'll be okay for a few months if I find myself unemployed again. There are a lot of guys who have it a lot worse than I do.
And if you take anything away from this comedy of errors, let it be that: this is the story of a guy who's doing okay in this economy.
Job: Imaging laptops, working in a warehouse, inventory duty
Distance from Home: 3.5 miles
Best Thing: Laid-back atmosphere most of the time
Worst Thing: Lung fungus
Length of Service: 2 years
This wasn't a bad gig, really. Not intellectually challenging, but I worked with some good people, I got some good exercise in, and most times things were pretty laid-back.
But it wasn't worth giving up my health for, and ultimately that's what I did.
I did a lot of work out in a dusty warehouse, and I managed to contract valley fever. For those of you not from around here, valley fever is a lung fungus, and it lives in dust. The Valley and valley fever are like the Internet and Hitler comparisons -- you stay there long enough, it's something you're eventually going to have to deal with.
So I contracted a lung fungus working there, and I've still got asthma. It's manageable now, but I'm not what I was. Before I took that job I was healthy.
The next-worst thing about the job, after the lung fungus, was the meddling from up the chain. People with little-to-no grasp of our actual day-to-day operations had very strong opinions of what those operations should be, and precisely which boxes we should check on which forms each and every single time we did them. Precisely what those opinions were tended to change from week-to-week, producing an ever-changing, increasingly complex system for dealing with very simple tasks.
And as this went on, the environment became less and less laid-back, and more and more stressful.
There was a real disconnect between the building I was in and management out on the west coast. Within my office I was regarded as an essential member of the team, and indeed my bosses not only recognized my value, they realized that I could probably be doing more for the company than just counting how many sticks of RAM were left in inventory, and fought hard to get me not only hired on but promoted.
It's no small comfort to me that every single person who actually worked with me was pulling for me. To the point that when Corporate decreed that all the temps would be let go, my boss's boss's boss got reassigned for telling his boss's boss's boss exactly how he felt about that.
It was nothing personal. And it was nothing to do with my performance. I was just caught up in a bloodbath. I was part of the first wave, but it kept going. Last I heard, they'd laid off another third of my department, every help desk tech in Arizona, nearly everyone in the front office, and most of the people up the chain to VP. And demoted my boss back down to tech.
But before all that, I got a layoff for Christmas. I lost my job two years, to the week, after I'd gotten it.
There's a fatalism that kicks in after awhile. A knowledge that no matter how hard you work and how much you're appreciated, there's some clown in a corner office somewhere who's never met you but has the power to decide whether you're drawing a paycheck next week.
But ultimately there's something liberating about that, too. After awhile you stop trying to impress the clowns in the corner offices who have never met you. You realize the only people worth giving two shits about are the ones you deal with every day -- and that trying to impress them isn't about whether you'll have a job next week, it's about doing a good job for its own sake and for the sake of your team.
Those guys had my back. And that means more to me than a paycheck ever did.
Unemployment sucks. But it could be worse.
It's a pretty damn smooth process in this day and age -- all online, no driving across town and waiting in line. You fill out an online form, they take a week or two to make sure your story checks out, and then they open up a bank account for you, send you a card, and put money in every week.
Once a week you'll have to resubmit your claim. You tell them you're still looking for work (and keep evidence on file in case they ask for it -- I kept rather a long Excel spreadsheet with a list of everybody I'd contacted) and declare any money you've earned.
The whole thing's demoralizing and more than a little Kafkaesque -- Ursula K Le Guin recently described it quite wonderfully in a short story called Ninety-Nine Weeks: A Fairy Tale, and it's barely an exaggeration. That spreadsheet I mentioned where I kept track of all the dozens jobs I applied for? Only one of them ever actually got me an offer, and it was out-of-state -- more on that below. By the time I did finally get work again, it wasn't from the job search, it was from the same temp agency I'd been working for since '08.
Job: Imaging laptops
Distance from Home: 13 miles
Best Thing: A job!
Worst Thing: Poor pay, sporadic availability
Length of Service: 3 months, off and on
This one wasn't too bad either. Neat office, nice people, and a certain degree of autonomy. The cramped little room I worked in got pretty crowded and hot as time went on, and there was a whole lot of downtime as I waited for laptops to finish imaging, but hey, I got time to catch up on my reading.
I also learned some interesting things about security policy. I've never had to lock things down so tightly from the BIOS -- a unique strong boot password on every machine, USB boot disabled, Bluetooth disabled, and on and on.
The toughest thing was that this wasn't a 40-hour-a-week job. It was "We just got these laptops in; image them and when you're done we'll send you home and call you back in when we get more."
And, without getting into the specifics of my pay, here's where that got frustrating: often I didn't make significantly more money than if I'd just stayed at home and collected unemployment.
Unemployment in Arizona works like this: you get a weekly stipend of up to $240. I was eligible for that maximum amount.
Every week, you report how much you've earned. You can earn up to $30 before they start subtracting your earnings from your unemployment check.
So there's this sort of dead zone between $30 and $270 where you are making the same amount of money whether you work or not.
And at this job, I frequently worked a weird part-time schedule and fell into that zone. Once I got past that first $30, I wasn't actually making any money; I was just getting a paycheck from the temp agency instead of the state.
Obviously there are still reasons to work. For its own sake, first of all. And second, to stay eligible for my healthcare, which was set to expire after three months without work. (I got back into the market just in time, but not fast enough to keep someone from fucking up my paperwork and taking me off their books even though I was still paying in every week. I had to call three different departments to get it corrected and my last prescription covered.) But there's still a definite sense of frustration in knowing that you're effectively working for free.
More than one other tech actually told me I should slow down and deliberately take longer to do the work so that I wouldn't get sent home in the middle of the week to await the next shipment. What a position to be in -- effectively being punished for being efficient, and incentivized to slow down and waste time.
This, as you will see, was to become a recurring theme.
Job: Phone support
Distance from Current Home: 30 miles
Distance from Apartment Where I Lived 4 Years Ago: Directly across the street
Best Thing: Coworkers seem like all right guys
Worst Thing: The single worst job I have ever had. Fuck these people.
Length of Service: About a month
On some level, this fucking fiasco was my own doing.
I'd been poking through listings on some job site or other (probably not CareerBuilder; I quit using it after I discovered it was the thing that kept locking up my browser and hanging my entire system) and I noticed an IT job being offered through my temp agency which my rep hadn't brought to my attention. So I E-Mailed him and asked about it. In hindsight, I should have assumed there was a good reason he hadn't approached me about it.
It was phone support. Not phone support like I'd done before, but in a phone bank -- I had a few feet of shelf that I wouldn't really refer to as a desk, partitioned off from the guys next to me by small dividers that I wouldn't really refer to as a cubicle. Every morning at 6 AM I pulled up whatever broken chair nobody was sitting in, put on a headset if it was still where I'd left it the day before, and started working my way through a list of branches to call to walk their managers through installing new kiosks that didn't work very well in buildings that, half the time, weren't cabled correctly. (Ever walk a retail manager through recabling a patch panel? I've done it six times before breakfast.) It was dimly lit and it was dehumanizing -- I'd compare it to an assembly line, but the assembly lines I've seen are a whole lot livelier and more fun.
(I will grant one thing to the "cog in a corporate machine" setup: this is a company with hundreds of stores, all organized exactly the same. Each store has the same patch panel with the same numbered ports that go to the same rooms and assign IP's based on the same scheme. There was this in-house .NET program we had that would let you plug in a store number, automatically populate the IP address for every port in the place, and give you a one-click ping for each one. That's the advantage of a company that treats its stores as unifom, cookie-cutter widgets. The disadvantage is that it treats people exactly the same way.)
I spent most of each day on hold listening to the same fucking 16 bars of piano music over and over again. Periodically interrupted by a recorded voice telling me I was on hold, of course -- and if I ever meet the son of a bitch who decided to stick voice recordings in the middle of hold music, I am going to gouge his eyes out with my thumbs. I know I'm on hold, asshole; that's why there is music playing. About the only thing that could trick me into thinking that I wasn't on hold would be if the music abruptly stopped and I heard a human voice instead.
There were a couple of guys there who I'd gone to high school with. One of them I recognized but hadn't really known very well; the other used to pick on me but claimed not to remember me (he blamed it on the drugs he'd been doing back then and I am inclined to believe him). Now, remember how earlier I expressed frustration that my career hasn't really gone anywhere? Well, if you want a symbol that will hammer that little insecurity home, suddenly finding yourself sitting next to a couple of guys from high school is a pretty good one. But probably not as good as being directly across the street from the apartment where you lived back when you worked a previous dead-end job. Man, that would have been a sweet commute in 2007!
So no, let's say that this job wasn't the best fit for me. But dammit, I got up every morning at 4:30, put on a smile, went in, did my job and did it well. I blew through every task they gave me and asked for more.
This, as it turned out, was a problem. But nobody ever actually bothered to tell me that.
One morning I walked in and found that my login wasn't working. I asked the guy who'd been training me; he hemmed and hawed and wandered off for awhile, then came back and told me to turn in my badge.
It bears repeating, at this point, that I had just driven 30 miles to show up to work at 6 AM.
My rep told me that they'd called his office the previous evening to tell him to call me and tell me not to come in to work in the morning -- after he'd already gone home for the day.
He added that I'd been sacked because they thought I didn't schmooze enough with the end users over the phone -- something that nobody had ever actually complained to me about. I wasn't rude, or even brusque; I was just, in my rep's words, "too focused on getting the job done". I'm used to support jobs emphasizing getting the task done quickly, because the user doesn't want to be on the phone and wants to get back to what she was doing. But apparently that's not how it worked at this company; they wanted me to slow down and shoot the breeze -- except nobody ever bothered to tell me that. Come on, guys, if you want me to talk about the weather, just say so -- I have quite a lot to say about the weather in Phoenix in June, even when half the state isn't on fire.
Anyhow, it's the only job I've ever been fired from. And nobody even bothered to tell me there was a problem, let alone that I'd been fired.
The guy who walked me to the door was apologetic and told me not to worry about it, that people get fired from that place all the time through no fault of their own; maybe just for looking at somebody the wrong way. And it occurred to me that I'd passed my boss early one morning in the hall and, when she asked how I was doing, cracked a grin and responded "Hanging in there" -- and she apparently took offense that I hadn't said something more enthusiastic.
On the whole, pretty demoralizing and upsetting, and far and away the worst professional experience I have ever had.
Of course, I use the term "professional" in its loosest possible sense.
Through it all, of course, I was interviewing wherever I could.
There are lots of stories I could tell. The temp agency I spent half an hour trying to find. The interview where I referred to a former coworker as "A temp like me, but kind of a slacker" but the interviewer just caught the "like me, kind of a slacker" part and that pretty well torpedoed me. The interviewer who asked me about a comment I'd posted about Spore's DRM on the FTC website back in '09 and then followed up by asking my opinion about SB1070. But the best story is the hosting company I saw advertised on a billboard.
"Do you know Linux? We're hiring!" said the billboard, with a colorful mascot next to the words. I would see it on the freeway on my way to work. Or maybe it was on my way home from work. Maybe it was both; I think they had more than one billboard.
Well, hell yeah I know Linux. I pulled up the website and submitted a resume. Turned out it was a hosting company -- even better. I spent most of '07 running the backend of a local ISP singlehandedly; I know my way around Apache httpd and MS IIS pretty well.
So they called me back, and the most immediately odd thing was that they told me the job was in Austin. Why would a company in Austin advertise in Phoenix?
Well, of course the answer is that they couldn't find anybody in Austin willing to accept the shitty salary they want to pay for Linux administration, so they're advertising in depressed markets that are full of desperate, unemployed Linux admins. But as you might expect, they didn't come right out and say that.
No, they gave me some talk about how they're expanding into new markets, and how they'd pay for my relocation, and they didn't balk when I gave them a deliberately high figure for my expected salary. They made the whole process seem very exclusive, putting me through three different interviews -- a general one, a second one with a series of technical questions, and a third where they had me SSH into one of their servers and demonstrate that I know my way around bash.
And then they offered me an hourly rate that was maybe fifty cents better than what I was currently getting in the phone bank. And a relocation fee that might have covered a U-Haul rental, deposit, and first month's rent on an apartment.
I hear Austin is a neat place, but no thank you.
It was about this point that I decided to read some employee testimonials on the place, and it sounded suspiciously like the terrible job I was already working at.
The billboards are down now. I wonder if they ever found anybody desperate or gullible enough to take their offer.
Job: Imaging laptops
Distance from Home: 32 miles
Best Thing: Getting work immediately after the previous fiasco; autonomy and people who were happy to see me
Worst Thing: Night crew fired after their first day
Length of Service: 6 weeks
Actually, before this job my rep sprang into action and got me a half-day gig fixing a company's QuickBooks setup, a mere 5 days after the debacle at my previous job. But I'm not counting that as its own section. My rep's cool, though.
Anyhow, shortly after the half-day QB fixer-upper, he found me something else and, at last, I got to be part of a Windows 7 refresh -- the precise thing that my boss, the previous December, had assured me would ensure my job security for another year, the week before announcing that the Windows 7 rollout had been canceled and so had my employment.
Anyhow, this one was interesting. The idea was to provide a minimum of disruption for the employees, while upgrading most of the office to Win7 in a matter of weeks.
So we had a night crew. They came in, ran a script to back up the user's files, either reimaged the user's existing computer or grabbed a new, freshly-imaged one that I'd already put together, restored from backup, and left it to me to walk the user through initial configuration the next morning.
At least, that's how we eventually got it working. The first night, things failed rather spectacularly.
I got in the next morning to find the night crew still there, a small handful of computers actually in working condition, and the rest in various states of completion.
The way I heard the story went something like this: one tech on the crew had asked the guy in charge what the plan was -- how they were going to split up the workload, what the schedule was, etc. He had made some vague "Just get started" noises. She asked him a few more times; he responded similarly. Finally she just went to work; she was responsible for the handful of machines that had actually been finished, while the other techs hadn't really worked out a plan for how to get their work done.
So the company fired everyone else and put her in charge of the new team.
After that it went really smoothly most nights. There were a couple exceptions -- one weekend when the generator had to be turned off for maintenance and so they couldn't come in to get computers ready for Monday, and one night when the AC was out and it was too hot to work. But no more problems from the techs themselves; the second crew did a really great job and made my life much easier.
Job: Imaging laptops
Distance from Home: 22.5 miles
Best Thing: Autonomy
Worst Thing: Still a bit of a drive.
Length of Service: 4 months so far, out of a one-year contract.
And from there I moved on to my fifth job of the year, not including freelance Web design or that one-day gig fixing QuickBooks.
This one comes with a one-year contract, so hopefully that'll hold and I'll still be there through next August. But I'm not going to take that for granted; one of the many lessons I learned in the Dank Pit of Phone Support last summer is that a six-month contract can turn into a one-month contract with absolutely no warning. Course, I've been working this one long enough that I am confident in saying that this time I am working for decent human beings, but again, it's not the people I've actually met I'm worried about. And every time I hear the Windows 7 rollout's been delayed, I get a little nervous.
I guess it's worth asking, what motivates me to come to work every day and do a good job? Here's what I can come up with:
It's instructive to note the things that aren't on the list. "Hope for promotion" and "fear of losing my job" are conspicuously absent -- yes, I do feel both of those things, but as I've mentioned several times, I have absolutely no sense that my employment or advancement is tied to my performance in any way. They're motivating factors just as much as the potential for finding a $100 bill on the ground or tripping and cracking my skull -- they're both things that have some potential for happening, and my job performance has about as much to do with the likelihood of either one.
Also missing: "company loyalty". And unlike those other two things, this isn't something I have in the slightest. I am, as I said, loyal to my coworkers, and I appreciate my rep at the temp agency, but that's not the same thing as being loyal to either the company I'm working for or the company that placed me there. If I get a better offer I'll take it -- and those last two bullet points are the only reasons I'll give two weeks' notice.
On the whole I'm not entirely sure this is a bad thing from my perspective -- hell, the ideal list would probably have two bullet points instead of four. Company loyalty, the stick of firing and the carrot of advancement -- I don't need those things to do a good job. But from the company's perspective, it's probably a bad thing.
And if I may be so bold, I think I'm probably representative of a good solid chunk of my generation. Educated, underemployed, unable to hold down a job for more than two years through no fault of my own -- what happens when that's your workforce? In the coming decades we're going to find out.