wonko.com

Hi! I'm Ryan Grove: Sorcerer at SmugMug, lover of movies, eater of pie, connoisseur of awesome.

Posts tagged with “work”

Displaying items 1 - 10 of 22

On working remotely

Yesterday, Yahoo! internally announced a new policy: no more remote workers.

[…]

Beginning in June, we’re asking all employees with work-from-home arrangements to work in Yahoo! offices. If this impacts you, your management has already been in touch with next steps. And, for the rest of us who occasionally have to stay home for the cable guy, please use your best judgment in the spirit of collaboration. Being a Yahoo isn’t just about your day-to-day job, it is about the interactions and experiences that are only possible in our offices.

[…]

Leaked Yahoo! email published by AllThingsD

This new policy is shockingly shortsighted, and is a significant step backwards for Yahoo!.

I worked remotely for Yahoo! for over three years, and I currently work remotely for SmugMug. During my time at Yahoo!, many of my most brilliant, passionate, and productive coworkers also worked remotely. Some of them are still there, and they’ll be affected by this policy.

The shocking thing about this policy is not that Yahoo!’s management thinks employees will be more productive, communicative, or creative if they work together in an office. In many cases, this is true. What’s shocking is that they seem to think this will be true in all cases.

It won’t, and I’d like to explain why.

Some people can’t work remotely

First, let’s acknowledge the obvious: not all jobs can be done remotely, and not all people are good remote workers.

My experience working remotely has been as an engineer. At times my job has involved close collaboration with many people — sometimes as a team lead — and at other times my role has been as a self-directed individual contributor. The latter is much easier to do remotely, while the former required a great deal of attention and care both on my part and on the part of my coworkers.

In general, I would not recommend trying to lead a team or manage a highly collaborative project as a remote worker. It’s possible, but it’s hard, not just for you but for the team.

Working remotely as an individual contributor has its own set of challenges, and still requires significant discipline, self direction, and communication.

I’ve known brilliant engineers who were terrible and unreliable remote workers because they were undisciplined or didn’t communicate effectively when not in an office setting. It’s virtually impossible to know whether someone will be a good remote worker until you try them.

Some people, when left to their own devices, lack the discipline to stay on task. Absent supervision and the physical presence of coworkers, they relax — consciously or unconsciously — and get less done.

They may justify it to themselves (“I got a lot done yesterday! I deserve a day off.”), or they may encounter an obstacle and use their remoteness as an excuse to procrastinate (“Crap, Sara’s the only one who knows how this code works and she’s not online right now…”), or they may simply be lazy.

I suspect this is one of the reasons behind Yahoo!’s policy shift. It’s notoriously difficult to fire someone at Yahoo!, and for that matter at many large companies. If you hire a remote worker and it later turns out they’re not cutting it, the best you can hope for is to require them to work from the office or try to get them transferred somewhere else in the company so they’ll be someone else’s problem.

Remote workers are more of a risk than non-remote workers, and you’ve got to be willing to let them go if things don’t work out.

Some people are much more effective remotely

Some people, when left to their own devices, become unstoppable forces of productivity.

I’m one of those people. Dav Glass is one of those people. So are Luke Smith, Eric Ferraiuolo, and others I’ve had the pleasure of working with over the years. The four of us all worked remotely for Yahoo! (Dav and Eric still do), and would occasionally take trips to the office.

We all found it virtually impossible to get anything done during our time on site. The difference in productivity was staggering, to the point where I ended up doing my best to finish as much work as possible before a trip so I wouldn’t fall behind while spending a week at the office dealing with constant interruptions and distractions.

Not everyone is like this. Some people thrive on face to face interactions and random hallway chats, and can handle frequent interruptions. The four of us, and many other remote workers like us, thrive on long stretches of quiet time alone, with limited interruptions.

But, most importantly, we have the discipline to stay on task, get our work done, and communicate frequently and effectively with our coworkers even though they aren’t physically present.

It’s about people, not locations

People are different. Jobs are different. Remote doesn’t work for everyone, but the office doesn’t work for everyone either. Some companies understand this and some don’t.

There was a time when Yahoo! seemed to understand this. They didn’t let just anyone work remotely, but they didn’t prohibit everyone from working remotely either. They understood that on a case by case basis, some people, in some jobs, could be excellent remote workers.

Telling effective and responsible remote workers that they can no longer work remotely — not because they’re bad at it, but because some other people might be bad at it — will only make those people less effective at their jobs.

Or it’ll make them leave and find better jobs at companies that see them as people with unique strengths and weaknesses rather than as homogeneous cogs in a corporate machine.

Feeling smug

Next week I start my new job at SmugMug!

This is old news if you follow me on Twitter. I plead laziness: I’ve spent much of the past two weeks sitting on the couch watching Magnum, P.I. on Netflix and generally avoiding any device with a physical keyboard.

During this time of reflection and relaxation, I’ve learned two things:

  1. Magnum, P.I. is awesome.
  2. iPads are awesome.

But seriously. SmugMug! I’m excited. This company is special in a way that’s hard to put into words.

On the day I visited, Beth the SmugChef surprised me with seven different kinds of pie. She had even scoured Felicity’s blog to find the recipe for my favorite, maple custard. When she set two plates full of pie in front of me at lunch, I knew I couldn’t possibly work anywhere else.

This feels right. I can’t wait to get started!

On Leaving Yahoo!

After five years, I will be leaving Yahoo! at the end of this month.

I’m not a fan of candy-coated, platitude-filled departure announcements that coyly avoid revealing actual opinions, so this is not one of those. I have many opinions about Yahoo!, and they have led to my decision to leave.

I’m not leaving to “explore new challenges” or “spend more time with my family”, and I’m not leaving because someone offered me a better job. I’m leaving because I no longer want to work for Yahoo!.

To be clear, I’m not leaving Yahoo! because I dislike my job, or my coworkers, or the projects I’ve been working on. I love my job. I love my coworkers. I love what I get to work on. For the past two years, I’ve had what is essentially my dream job working on YUI. Nothing I’ve ever done has been as much fun or as fulfilling as getting to wake up every morning and spend all day making one of the world’s awesomest open source JavaScript libraries a little bit awesomer.

What other job would pay me to write open source code, design, build, and perform sysadmin duties on a popular website, and even shoot and edit videos (one of my favorite hobbies)?

But as much as I love YUI, the team behind it, and the fantastic community of third-party contributors and users, I no longer believe in Yahoo! as a company. Yahoo!‘s corporate goals have taken some alarming turns recently, in particular with the reprehensible patent lawsuit against Facebook and the most recent round of senseless layoffs. Yahoo!’s actions violate my personal values and don’t reflect the values of the company I joined five years ago.

That said, my time at Yahoo! has been amazing, and I’m not exaggerating. When I joined Yahoo!, I thought I was hot shit. I wasn’t. I’ve learned and grown more as an engineer and as a person in the past five years than at any other time in my career. I’m grateful to have gotten to work on so many interesting projects with so many talented people. I don’t regret my time here.

Yahoo! has treated me well, both as an employee and as a human being. My managers and coworkers rewarded me and recognized me when I did great work and gave me honest criticism and guidance when I needed it.

When I told my manager in 2008 that living in the Bay Area wasn’t working out for me and Felicity and that I wanted to work remotely from Portland, Yahoo! was incredibly flexible and accommodating. They didn’t have to let me do that, but they did, and I’m very grateful.

When I’ve taken huge risks (like the time I developed and launched Yahoo! Search for iPhone — and announced it on my blog — without asking permission), Yahoo! has backed me up. Those gambles didn’t always pan out, and sometimes I got privately scolded, but I was never punished for pushing through the bureaucracy to do what I thought was the right thing, and in many cases I was rewarded. I respect Yahoo! for that, even though I wish it hadn’t been necessary.

I still think Yahoo! is a great place to work, and I mean that; the YUI team in particular (hint, hint). It’s just not the right place for me.

I don’t know what I’ll do next. I’m thinking about that now. If you’re looking for an awesome frontend engineer in the Portland area or are open to remote workers, get in touch.

Update (April 16): I’ve been completely swamped with job opportunities since this post went up. If you’ve reached out to me about a job, thank you! I feel incredibly fortunate to have so many exciting possibilities in front of me.

There have been way more opportunities than I can possibly pursue over the next few weeks, so I’ve had to start declining requests for coffee, phone chats, etc. If you haven’t already gotten in touch with me, please hold off for now.

It feels really weird to ask that people stop throwing fantastic opportunities at me, but I’ve spent the past few days answering emails and phone calls almost non-stop, when I should really be focusing on finishing up my work at Yahoo!. Thank you again to everyone who’s contacted me. I really appreciate it!

YUI!

A little over three years ago, I opened a purple box containing a job offer and some boring forms to sign. It yodeled at me when I opened it. That’s when I knew I’d made the right choice in deciding to join Yahoo!.

Working on Yahoo! Search has been an incredible experience. I can now say that I’ve written code that’s used by hundreds of millions of people around the world. I can also say that I’ve broken code that’s used by hundreds of millions of people around the world (fortunately that only happened once). During my time there I did a little bit of everything, from writing build tools and pushing pixels around for bucket tests to leading frontend development on the September 2009 Search redesign—the biggest in the history of Yahoo! Search—which the team managed to pull off in only a matter of months.

At its best, working on Search was exciting and fulfilling in a way no other job has been for me; at its worst, it was stressful and relentlessly demanding. But whether it was exciting or stressful, fulfilling or demanding, I always learned something new every day, and I got to work with some of the smartest people in the business. As far as I’m concerned, that’s what makes a thing worth doing.

It’s in this spirit that I’m launching myself on a new journey. Not an altogether different one—I’ll still be at Yahoo!—but certainly one that I expect will be both incredibly challenging and a lot of fun. As a member of the YUI team, I’ll get to work on an awesome project that I love, with awesome people from whom I will doubtless learn truly epic amounts of stuff on a daily basis.

A little over three years ago, if someone had told me I’d be this lucky, I wouldn’t have believed them.

Working from home

I’ve been working from home full time for about five months now. At times it’s been relaxing, other times it’s been stressful; sometimes convenient, sometimes less so. Here are some things I like and some I don’t.

The Good

  • No commute. This is huge. My stress level dropped through the floor when I stopped having to deal with 45 minutes or more of California drivers twice a day. The extra time at the beginning and end of my workday can now be used for other things, like sleeping in or cooking dinner. I also save on gas by never having to drive anywhere.
  • More time in the “zone”. Without anyone dropping by my cubicle to chat or distracting me by chatting with other coworkers nearby, I find it much easier to concentrate. Email and IM are my biggest distractions now, but they’re easier to deal with than a chatty coworker. This really adds up; I’m a lot more productive working from home than I ever was in the office.
  • I eat better. I’ve lost weight over the last few months just by cutting the Yahoo! cafeteria out of my diet and eating fewer lazy microwave dinners.
  • More freedom. If I want to take a break in the middle of the day to exercise, cook a meal, play with the cat, or just relax, it’s much easier than when I’m at the office. I definitely don’t take advantage of this as often as I should, but at least I know I can if I need to.

The Bad

  • Harder to connect with coworkers. I knew most of my coworkers pretty well before I started working remotely, but it’s hard to establish a rapport with newer team members who joined after I moved. One project manager even asked me who I was when I started to explain something in a meeting during one of my trips to the office. She had never seen me before, so to her I was some random guy who just showed up and started acting like he knew stuff.
  • Close collaboration is harder. IM and IRC are okay for loose collaboration, such as when several developers are working on different parts of an application or are acting as individual contributors to various projects. But for close collaboration in which multiple developers need to work on or review the same piece of code, or when a cross-functional team needs to collaborate on hashing out a design change or a feature spec, the inability to be in the same room is frustrating.
  • Meetings suck more. I attend roughly the same number of meetings now as I did before, only now I do so by phone, using Adobe Connect for screen sharing when necessary. In addition to all the usual reasons why meetings suck, remote meetings add crappy sound quality and an inability to see or hear the reactions of the people on the other end of the line when you’re speaking.

The Blurry Line Between Work and Play

I write code for a living. I also write code as a hobby. This means I often spend all day sitting at a computer writing code; the first part of the day for work, the second part for fun. It’s easy to let the work part of my day extend into what should be the fun part of my day, so I have to set certain boundaries. I’ve evolved a few life hacks that help.

First, I have two laptops: one is my work laptop, one is my personal laptop. I only use the work laptop for work, and I only use the personal laptop for non-work. When I’m done with work for the day, I turn off my work laptop and put it away to avoid the temptation to check my work email or something silly like that, which would likely result in me getting sucked back into work when I should be relaxing.

Second, when I’m working, I work in my home office with the door closed. When I’m not working but am still doing computery things, I either open the door to my office or go sit on the couch with my personal laptop. The open/closed status of my office door helps change the feel of the room from a place of business to a part of my house, and when even that’s not enough, relaxing on the couch usually does the trick. I’m pretty sure the cat has picked up on this too; she rarely bothers me when I’m working, but she seems to know she’s more likely to get attention when I’m not working.

Finally, I don’t work on weekends or holidays, period. No matter what. Even if I’m bored out of my skull and would rather be working. I’ve been tempted, but so far I’ve always managed to resist. I know that as soon as I start letting work intrude on my days off, I’ll launch myself down a slippery slope.

All things considered, I do prefer working remotely, and I’ve found that flying to California every six weeks to spend five days working in the office helps mitigate the drawbacks.

Customer service

Every so often, perhaps once every few months, I’ll get a call at my desk from a Yahoo! customer who has dialed the company switchboard and then punched in a random extension in the hopes of reaching a human who can help them with a problem.

In a perfect world, this would be a reasonable strategy. In a perfect world, I would know everything about every Yahoo! product, I would be able to help this poor desperate customer, and then maybe they would tell their friends what a great company Yahoo! is because they randomly dialed a developer who was happy to give them the help they needed.

Unfortunately, the world is not perfect and I don’t know everything about every Yahoo! product. I don’t even know everything about the product I work on. The odds that someone with a question about Search Assist would dial a random number and actually reach me rather than one of the other 14,000 Yahoo! employees are infinitesimally small. So, naturally, the people who randomly dial my number invariably ask questions about products that I know nothing about.

By the time someone resorts to dialing random numbers, they’re pretty desperate. Sometimes they’re very upset. They don’t care that I’m a developer working on something completely unrelated to whatever it is they’re having a problem with; to them, I am the human personification of Yahoo! the Big Faceless Corporation, and they expect me to have at my fingertips the entirety of Yahoo’s corporate knowledge.

When I explain that I can’t help them, they expect me to be able to transfer them to someone who can, and they find it incomprehensible that, as a Yahoo! insider, I don’t have a handy list of Top Secret support phone numbers. Sometimes this makes them angrier, and sometimes this makes them ask again really, really nicely in the hopes that I’ll decide to rebel against my cruel superiors and transfer them to one of the Top Secret numbers.

In the end, I’m unable to help these desperate people. I give them the premium support phone number (which is for paying customers), but usually the questions they’re asking are about a free product, for which (as far as I know) there is no phone support.

It’s not that Yahoo! doesn’t care; we do. It’s just that there’s no way we could possibly hire enough human beings to provide personal support for every one of our hundreds of millions of users (most of whom are using free products). It’s a simple problem of scale; no company in the world could afford this. Not even Google. Not even Microsoft.

Even so, whenever this happens, it pretty much ruins my day.

Obligatory disclaimer: the opinions expressed in this post are mine alone and do not represent the views of my employer.

Sketchy recruiting tactics

Even before the whole Microsoft thing, Yahoo! was a prime target for recruiters. A recruiter will find someone’s website or LinkedIn profile, discover that they work for Yahoo!, then call one of the main Yahoo! numbers and either drill through the directory to find the person’s extension or simply ask a receptionist to transfer them. The end result is that whenever my desk phone rings, there’s a 90% chance it’s a recruiter.

On the whole, I don’t mind being pinged by recruiters via email or on LinkedIn. If they’ve actually seen my résumé, then they know my cell number, which they’re welcome to call as well. But my work number isn’t published anywhere, so when I get recruiting calls there, it’s extra annoying and doesn’t do much to establish a feeling of trust.

So, to avoid these annoying interruptions, I’ve simply stopped answering calls from numbers I don’t recognize, and I’ve updated my outgoing voicemail greeting thusly:

Hi, this is Ryan. I’m not at my desk right now, but if you leave a message I’ll try to get back to you. If you’re a recruiter, please hang up now.

Even so, I still get voicemails from recruiters. The ones who actually hear the message usually say, “I know your message said to hang up, but…” Some of them stoop to really sketchy levels, like giving only their first name (to imply that I should know them) and saying that “some important papers” have recently come across their desk and that I should call them right away. One woman left several messages like this and I eventually had to call her back just to tell her to stop.

But none of these comes close to a voicemail I got a few weeks ago from a guy who appears to have seen this site and thought (correctly) that talking about pie would get my attention. Unfortunately, he made the mistake of talking about pie while sounding like a creepy-ass pedophile:

Listen to the voicemail

I didn’t call him back.

Poetry gets results

When a new employee joins Yahoo!, they get to choose whether they want a PC laptop or a MacBook Pro. Unfortunately, if you choose a PC and then later decide you want to switch to a MacBook, there’s a huge waiting list (unsurprisingly, there’s no wait to switch from a MacBook to a PC).

Way back in November, my coworker Brett filed an IT request to switch to a MacBook. About a week later I filed one as well. We each got responses letting us know that we’d been added to the queue, that we could expect our MacBooks in Q1 ‘08, and that we’d get a status update in January.

When January rolled around and no status update appeared, I added a comment to my ticket requesting an update, but never got a response. In early February, I again requested an update. Still no response. Yesterday I decided to pull out the big guns. I resolved to post a poem to the ticket once a week until IT responded.

At 11am on Thursday, I posted the following limerick:

I filed an IT request
A response was promised with zest
When layoffs occurred
And Microsoft merged,
My ticket was lost in the mess.

By 11:13 the ticket had been assigned, and this morning I had a shiny new MacBook Pro.

Needless to say, Brett wasn’t too happy, since he’d filed his ticket before mine and should have been earlier in the queue. Luckily I had already written a haiku (having anticipated that the limerick would be ignored), so I suggested he post it to his ticket:

A MacBook request
filed in winter, long ago;
spring is drawing near

He posted it this morning and IT contacted him this afternoon to let him know his MacBook was being set up.

Result!