I Hate It Here

I hate my job. There it is.  This is not news.  In fact, this has pretty much been par for the course for most of the last fifteen years. 

This blog post nails it – if a job was fun they wouldn’t have to pay people to do it.  To quote in bulk:

Right now I have what by any criteria would be considered a good job. I’m paid decently, I have basic benefits, and the position is as close to Stable as jobs get these days. Yet I’m not happy because I’m expecting the job to make me happy. I expect it to not suck, when in reality on many days it does suck because it’s a goddamn job. Nowhere was I promised that it would be rewarding and fun all the time, or that it wouldn’t be frustrating, or that I would have days where I come home and wonder why I bother. I bother because they pay me, and getting paid is very useful to me. But that’s it. That’s the deal: I show up and fulfill my responsibilities, and then I get a check. Nobody said anything about fun.

As often as I give this advice to other people, I give it to myself lately. What I can’t figure out is why people in my age group (or younger) have this idea that the task for which they get paid will also be personally enriching. Is it because we lack fulfillment in our personal lives? Is it because we’re spoiled, believing that the working world owes us self-actualization in addition to a means of supporting ourselves? I’m not sure. What is certain is that we should be careful what we wish for. Those factory jobs that no longer exist start to look pretty appealing as our Career-as-Spirit Quest theory runs into reality.

It’s like this blog – I do it, I enjoy doing it, but it’s not something really monetizable.  Because to do that, I’d need to go out and hustle ads, I’d need to produce a base minimum of content, I’d have to start tailoring my output to maximize page views and draw traffic, and next thing you know, I’m not blogging anymore.  I enjoy writing what I feel like, when I feel like it, and I’m pretty sure that shortly after having to meet a deadline on SEO-maximized topics day in and day out, I’d wind up hating it.

When I took my first full-time job out of grad school, I remembered telling people that my job was as easy and profitable as picking up money in the street. It didn’t take that long to change, largely because our management situation melted down within a year to the point that our lead tech was reporting directly to an out-of-touch and irrationally unreasonable vice president.  But thanks to the foxhole mentality and the relentless churn of the dot-com era, we were quick to build a team of techs that weren’t just whip-smart and capable, but pleasant to work with and a boost to morale (lest we forget, “morale” is a measure of “how people are doing when they aren’t doing well at all,” to quote PJ O’Rourke, who famously pointed out that you never hear about the morale of people on spring break or at vacation resorts, just prisoners and soldiers and the like). 

So what would make my job suck less?

To borrow from Great Place To Work, employees believe they work for great organizations when they consistently:

1) Trust the people they work for;

2) Have pride in what they do, and

3) Enjoy the people they work with.

Well?

1) This is tricky.  I was lucky to direct-report to the greatest manager I ever knew for most of the first seven years out of school.  Since then it’s been a mixed bag – and almost without fail, my management from the director level up tends to be indifferent at best and actively antagonistic at worst.  The most constant problem in IT support comes from management that fixates on “customer service” and interprets it as how good we make the end-user feel rather whether the problem was resolved successfully and in the timeliest possible manner.  This frequently stems from managers who aren’t technical enough to understand the problems their staff is solving, along with the misbegotten notion that a company’s IT staff is providing a customer service to their co-workers instead of a peer function.  I never hear anybody going on about whether the electricians or the security or the custodial staff are providing excellent customer service.

2) I’m Winston Wolf.  I solve problems.  May I come in?  I daresay the one thing I do better than anything else in the workplace is solve problems – if you have a thing that needs to be made to work, or linked or integrated or just figured out, I’m your guy.  And inasmuch as I do that, I enjoy it and take pride in my success.  If there’s a real live disaster and I have to shovel coal twelve hours a day for a week to save our asses, I take pride in that too.  What I don’t take pride in is having to spend those twelve hours mopping up somebody else’s foreseeable mistake, or cleaning up from a disaster that we saw coming and which management ignored.  And I certainly don’t take pride in an endless array of having to walk around hand-holding the kind of people who never think to try rebooting the computer or sit in front of an open browser window with the cursor in the address field and ask “how do I get to webmail?”  (HINT: the address is webmail.company.domain, and if you were to just type “webmail” and hit return, YOU WOULD ACTUALLY GET THERE.)  Inasmuch as tech support is about problem-solving, I enjoy it.  Inasmuch as it’s a blend of babysitting and veterinary medicine, I hate it.

3) This is the problem…there are two splits here.  One is co-workers, and one is end-users.  End-users are always a problem.  Some are worse than others, some are really a pleasure to work with, but as the computing environment has evolved over the years, less stuff breaks.  We’re not using Token Ring some places and Ethernet others, we’re not struggling with System 7 and trying to make TCP/IP work reliable and trying to pass AppleTalk so people can print, we’re not running Windows NT 4 and terrified every time the virus alert pings.  Ten years of Windows XP, for better or worse, led to most of the rough edges being filed off, while OS X has gotten more robust and reliable with every passing release.  It’s reached a point where support issues, especially with a Macintosh, are only occasionally about “something is wrong with the computer,” and even those are mostly about a Java plugin that stopped working or a printer that requires deleting the queue and setting up a fresh connection – things that any user with admin rights ought to be able to figure out and fix themselves in 5 minutes.  And in the case of the younger users, they pretty much do.  That’s why I think the job is going away in ten years – partly because the technology is simplifying, but also in part because the generation that entered the workplace before their computers did is finally starting to retire and go away. Ten more years will be thirty years since I was in college, at which point it can be safely assumed that anyone in an office workplace has been using computers in an office since they started working.

The other split is co-workers, and here I was ruined, because my teammates at the first job were the perfect crew.  Replicating that has proven impossible, largely because we failed to weed out the toxic people quickly enough at my first California job and because I haven’t really had that peer-group environment since.  When everyone’s responsible for their own area, there’s commiseration, but not that common experience, that banding-together-against-the-common-foe.  Right now, I have a decent enough group of folks, but few if any are the sort of people I’d want to spend 8 hours at the Four Provinces singing and getting knee-walking drunk alongside.

So what’s the solution?  Right now, the plan is to agitate to move within this existing employer to a job with more future-proofing – something in data center or infrastructure administration, something that will still be necessary when all work is being dictated into iWatches from your home-working desk.  Something that will get me away from a customer-facing environment, something less interrupt-driven (well, slightly) and more project oriented, something not keyed to the workday hours of a call center.  And in the meantime, 5 PM means work is done, not to even be thought about until 8:30 the next morning (or Monday as the case may be).

Maybe this is all just project-related stress. Maybe once encryption is over and done with, it’ll be possible to have a more normal relationship with work.  But given that this was pretty much my situation and feeling for most of 2012, I suspect probably not.  This isn’t run-of-the-mill dysthymia either.  I don’t need antidepressants, I need something for stress.  And probably a ton of Xanax.  And let’s face it, a couple of cocktails wouldn’t hurt at all.  Not likely in the near future.  Of which, etc.

 

Too big for their britches

No one who lived through high tech in the 1990s will ever entirely trust Microsoft, or view them as other than a threat.  The Beast of Redmond used its effective monopoly for PC operating systems to leverage an effective monopoly in productivity software (killing the likes of WordPerfect or Lotus 1-2-3 as alternatives) and then used the Windows-Office duopoly to control the personal computing industry. They missed the boat on web browsing, and then bought Spyglass’s commercial Mosaic code to turn into Internet Explorer – and knit it into the operating system to crowd out Netscape, with the side-effect of intro ducting vectors of vulnerability that would provide ten years of malware vulnerability.  They invested a mere $150 million in Apple for the sake of propping up the only other viable commercial operating system maker – and in return Apple got continuing production of Microsoft Office for Mac, because without it the Macintosh would have been doomed quickly as a platform.

Things are different now.  Companies like Google and Facebook don’t have a monopoly as such – there’s nothing preventing you from using Yahoo for email or Duck Duck Go for web search or Path for social networking.  What Google and Facebook do have is a crippling majority of mindshare, and the sense in Facebook’s case that you have to be there because everyone else is, while in Google’s case, you’ve probably relied on their services (which have been largely excellent for many years) to the point that you’ve given them a critical mass of data.

Google and Facebook don’t charge end users at the point of service. Essentially, the only way you can give Google money is by buying a Nexus device – even Android is free and open-source at the OS level (the Google-specific apps for Android may still be proprietary).  Facebook is constantly smacking down rumors that they’re going to start charging, but by and large the only way to give Facebook money is to pay to promote a post. Or…to advertise.

I often wonder whether Google and/or Facebook can’t charge end-users for their service. Think about it – if Google or Facebook got rid of advertising and just charged the necessary amount to make up the difference, how many people would stick with it?  And more to the point, could you make as much money just by charging what the market will bear?  Or is this a situation where Google and/or Facebook’s services are provided as a loss leader to allow them to harvest enough personal information to make a profit at advertising?

Microsoft certainly thinks so – they pitched their new Outlook.com email service with some risible ads about “Scroogling”  as if they are shocked, shocked that a technology company would take unfair advantage of their position to make more money.  Frankly they ought to be more worried about getting their uptime on Outlook.com above three nines, but that’s neither here nor there.  Microsoft is finally paying the price for having sat on their laurels after the launch of Windows XP, while Apple was skating off toward the iPod and then the iPhone and then the iPad, and Microsoft shat the bed with the Zune and took forever to produce Windows Phone 7 and then whored all its buyers with Windows Phone 8.  And then Surface…erm, surfaced. Essentially, Microsoft is still stuck into the idea of Windows everywhere and Windows everything, one ring to rule them all.

By contrast, Google’s one thing is its ability to aggregate data and sell advertising.  And they will do anything that feeds into that, and kill it gladly if it doesn’t work out.  Sic transit Google Wave, Google Buzz, Orkut. That’s why Google+ will hang on.  That’s why they’re happy to put a superior Google Maps product on the iPhone instead of keeping it themselves as an Android differentiator. Google doesn’t care if they make money on the bait; their money’s in the trap.  Which is the same reason why Facebook keeps adding things like voice chat and video calling, and is urging on Graph Search (which is basically asking you to make your life an open book for the sake of improving search results).  Everything Apple (and Amazon) does is about getting you to buy more Apple (or Amazon) stuff; everything Google and Facebook do is about getting you to let them sell more of you.  That’s why Google Maps and the Kindle app are available on iOS – Apple knows that you’re more likely to buy an iPad if it can be a Kindle reader too, and Amazon knows it will sell more Kindle books if it can sell to more people than just own a Kindle device.  Similarly, Google wants mapping information from more people than own Android devices, and Apple would rather you buy an iPhone and run Google Maps than buy an Android device to do so.

But at least with Apple and Amazon, they’re still charging cash on the barrelhead in the time-honored market tradition of “money can be exchanged for goods and services.” Google and Facebook are still dueling for the right to your online identity – e.g. Facebook Connect or the all-new Google+ Sign-In – and to make themselves the intermediary of your online experience.  Hell, Google’s new Chromebook Pixel charges you MacBook Air money for what is essentially a browser terminal, but has one terabyte of cloud storage connected. One terabyte of your stuff…to be stored by Google.  The mind reels.

The moral of the story is this: if you are in fact the product, you have to avoid letting yourself get locked into a single solution.  Putting your entire life in Google is hella convenient and easy to use, but to quote Spencer Hall, “there is always free cheese in the trap, and it is always a deal.”  You don’t have to let yourself be the product. Google and Facebook may be too big for their britches, but they don’t have to be too big for yours.  If privacy and control are important to you, they’re worth paying for.

iWhat?

Bloomberg appears to have decided to will an “iWatch” into existence today, and everyone is running with their report – apparently the nonexistent iWatch is a better investment for them than the nonexistent iTelevision, and the fact that they are advising investors on the merits of products that do not exist is just one more reason why the investor class should be ground up into free meatloaf for the unemployed. But I digress.

The problem is, I’m still struggling with the use case for a notional “iWatch”.  With Google Glass, as I mentioned previously, the model is JARVIS – Tony Stark’s real-time artificial-intelligence assistant tied to a voice and HUD interface in the Iron Man armor.  The idea of being able to look at something, have it identified and pop up its Wikipedia entry instantly? I like that.  Not to mention real-time navigation and directions, possibly tied right to my calendar and incorporating things like traffic and train delays. “Sir, you need to leave NOW if you are to make the connection at Millbrae in time for the Warriors game.”

But the watch?  What would I like to be able to see on the watch?  Well, notifications, I suppose – it would be nice not to have to take the phone out to see who’s calling or who just texted me.  I suppose there are worse things than having a couple of canned replies available from the watch as well. (On my way, etc)  It might be handy to have calendar events visible and reminder alerts for same.  Plus having the wrist alerting might be more reliable than the phantom vibrate that we feel for no reason (or the real one we don’t).

The other trick is Bluetooth 4.0, of course.  What’s the range?  Would this mean alerts in the shower while the phone is outside on the sink counter? (Assuming a similar degree of waterproofing as the Pebble, or my own watch.) How long before you have to charge the watch? Once a week is fine – pop it on the charger overnight on Saturday night – but if it’s only 3 or 4 days, that’s problematic.  And how much power does Bluetooth 4.0 draw?  Are the savings from not taking out the phone and lighting up that big screen going to be wasted in maintaining the Bluetooth connection?  If the early returns on the Pebble are anything to go by, very possibly.

So what does that leave?  Some of the Fitbit/Fuelband-type stuff, maybe?  Activity tracking, sleep monitor, count steps and miles run and etc?  Okay, sure, might be useful especially as I work to get in better shape.  But enough to make it worth spending the money? Maybe if everything is rolled in together…at this point, I can see the appeal in waiting for the Apple version of such a device.  It may not be feature-complete in its first incarnation, but those features will work.  It’s like the original iPhone: no cut and paste, no 3G, no GPS no 3rd-party application SDK, but largely because those features couldn’t be implemented well or without compromising the battery.  The features that it did ship with were well-implemented, which seems to be the difference.  Google (and through them Samsung) will release a boatload of features and let you beta-test for them; Apple will release a limited device that does only the things it can do and do them well.

And maybe they’ll come up with some way of making those things make sense, and come up with some function I didn’t know I needed until I can’t live without it.  But until then, I’ll stick with what I’ve got…