End of an Era (for me)

On Friday I’ll be leaving my job at Automattic, and my position in the WordPress community. I’ve poured my life into WordPress for 8 years, longer than I’ve ever stuck around at anything else, and it will be super weird to lose a job, a social circle, and an all-encompassing everything all at once. But while this wasn’t a change I had planned on (well, only planned for 3 weeks, anyway) I know that it will be better for me.

For the next month I am going to focus on getting my health in shape under my doctor’s care — it went to hell during my a8c tenure for various reasons — and figuring out what I need to do to go back and finish up the degree I was a month from obtaining before I walked away from it to work on the prototype that would become WordPress 2.7. Also, I’ll finally rip up the invasive plants in my yard and put in a garden and some native plants. And I’ll keep doing acupuncture. I’ll probably start writing again. Practice Spanish. Maybe re-learn how to play the guitar enough for a backyard singalong or two.

After that, we’ll see. Maybe a new ux or product challenge. Maybe something different. Maybe leave tech altogether. I’m not really going to think about it much until a month has passed, because I don’t want to jump into something else right away and perpetuate the same overwork patterns I developed over the last 8 years. Habits take time to break. I might take some of that time to write up some of the thoughts I never got around to publishing while I was on the job or to answer any questions that I get asked more than once. Or I might just sit outside feeding stray cats. Who knows?

My wordpress.org email address will not work anymore. If you want to reach me and don’t have my personal email address, you can use the contact form on this site or @jenmylo on Twitter. If you’re a “But I want proof we are connected!” person, I’m on LinkedIn. If you’re a Facebook junkie, I really don’t use it — it gets my Twitter feed but I don’t monitor comments on Facebook or anything like that. I should really just turn off the Twitter feed, probably. So many things to think about when everything changes! Hey, and now I can update my gravatar when my hair changes color, since I won’t be going to WordCamps where I want people to recognize me from online. Maybe I’ll do that next week. Maybe I should pick a new color first. Or go back to purple. So many decisions!

Anyway, to everyone in the WordPress community who enriched my life in some way over the past 8 years, thank you, and maybe we’ll run into each other again sometime. If you’re ever in Portland (Oregon, not Maine) and want to get a chai or Ethiopian food or come feed a stray cat in the backyard, let me know!

Automatticians at WordCamps

Automattic is getting pretty big, almost 200 folks now, spread all over the world. That’s a lot of people we can send to WordCamps. I remember when it was mostly Matt and I splitting up who’d go to which events — how times have changed in five years!

Since we’re hiring so enthusiastically, my team is putting together a little guide for Automatticians on how to be an awesome Automattic representative at a WordCamp. I have a pretty giant list of tips and advice at the ready (you’d never have guessed, I know), but it occurs to me that non-Automatticians are probably the best people to ask about what we can do better when we pop in to a local WordCamp.

Here are some of the things from my giant list so far:

  • Don’t travel in packs. When there are a few or a bunch of Automatticians at an event, we tend to cluster together because we so rarely get to see each other — and we like each other — but it makes it less likely that we’ll meet new community members. 1. Because we’re too busy talking to each other to reach out to new people. 2. Because it’s intimidating for someone new to break into that group.
  • Ask questions. A lot of WordCamp attendees will already know about Automattic, so while we should definitely be a resource for anyone interested in the company, the better use of time is getting to know the community members: who are they, how are they using WordPress, what would help them make their community more vibrant, who are the local independent consultants/themers/developers that we should know about?
  • Help out. WordCamps are a lot of work. Automatticians aren’t visiting dignitaries — we’re getting paid to be there — and we should help out along with the locals, whether that’s taking a shift on the help desk, moving chairs, or passing out shirts.
  • Be identifiable. Wearing the same WordPress t-shirt as everyone else is cool and all, but wearing a shirt that identifies the wearer as an Automattic employee, or a lanyard for the badge or something, would make it easier for people interested in talking about Automattic (especially people interested in jobs!) to find the Automatticians in the crowd.
  • Carry cards. Saying “email me later” works better when the card with an email address is handed over at the same time. That said, getting community member contact info so the burden of follow-up isn’t on them is even better.
  • Tweet It.  Using Twitter to let local followers know Automatticians are there is helpful. They might love to meet in person and talk about working at Automattic or contributing to the .org project and may not realize we’re there, especially if we’re not on the speaker list.
  • Don’t hog the speaker slots. Yes, Automatticians are speakers you can rely on, and we do employ a lot of seriously smart people, but if the speaker roster is filled up with Automatticians, that doesn’t do a lot to help grow the experience of local folks, which is part of what WordCamps are about.
  • Don’t be exclusionary. If planning to go off to an Automattician dinner or something after a long day of not traveling as a pack, don’t make those plans in front of other people, who will feel excluded (or might not understand what’s happening and might inadvertently show up later and crash the dinner); make private plans in private via Automattic channels. Even better, don’t go to private dinners, go to dinner with members of the local community.
  • Be present. In sessions, don’t work on the laptop, just pay attention to the speaker. In the crowd, don’t focus on the phone, smile and meet new people. Be there for the whole event, don’t take off early or skip the second day. Show the local community that Automatticians are respectful and want to be there.

What would you add? In the comments (or in an email to me at jenmylo/wordpress.org if you don’t want people to see what you think) make suggestions for what Automatticians can do to be awesome at WordCamps. It’s also okay to give examples of times when we have not been awesome. Learning from our mistakes is good, too. Thanks in advance for your help!

Changes

Today I turn 41. It’s also the end of my quasi-leave of absence, and on Monday I’ll be returning to full-time work at Automattic on the Dot Org Team. When I do so, it will be in a new role; I’m posting about it here so that all concerned will know what I’m doing, why, and that yes, it’s intentional.

For 4+ years, I was the UX/Design lead for core. At some point in the first year or so, I also started project managing the core team/core development. Then I started doing some community work, events, and general contributor community management. There were also other things here and there, like trademark for a while, being the team lead of the Dot Org Team at Automattic, and various design forays. You might remember that this was too much. I’m not ashamed to admit that I burned out, and needed a break.

It’s my birthday, so it’s a natural time to reflect on where I’ve come from, where I’m at, and where I’m going. When Matt convinced me to take the job at Automattic, one of the things that got me in was that he said I could work on programs to bring women and girls into the WordPress community, especially around programming. In that lunch on a San Francisco sidewalk, I laid out a vision including mentoring programs, school projects, summer camps, trips to the moon… okay, not trips to the moon, but just about everything under it. And then I never did any of those things because I didn’t prioritize it over my work on core.

Don’t get me wrong, I still think core is mega-important. Core *is* WordPress. Without it there would be no community. That said, core doesn’t need me to pour my life into it; my offering feedback, some sketching, and advice occasionally can be as much of a help as my doing research, creating wireframes, reviewing every trac ticket, and testing every ui patch.

In 3.5, I was meant to be on leave (aside from the summit planning), so I  answered some questions and gave some feedback early in the cycle to Dave/Helen/Chelsea/Koop, but otherwise stayed out of it. (P.S. Kudos to Nacin on the project management of 3.5!) My only real involvement was at the end of the community summit, when I spent several hours the last morning sitting with Koop going though the media uploader screen by screen, asking questions (“What about _____?” “What problem does that solve?”), sketching alternate approaches, and generally dumping every reaction and idea I had about it into Koop’s head before he left for the airport. Then I didn’t think about it again. From Skype a few weeks later:

Andrew Nacin 11/27/12 12:28 PM
feeling good about 3.5?

Jane Wells 11/27/12 12:31 PM
i wasn’t really involved with it aside from media morning with koop before he left tybee

Andrew Nacin 11/27/12 12:31 PM
that morning was huge. completely re-shaped a lot of our thinking.

That has me thinking that 4 hours here and there will do just fine instead of ALL THE HOURS.

So! Where does that leave me, if I don’t need to do core design or project management anymore? I keep going back to that sidewalk lunch and how exciting it was to talk about possibilities around using WordPress as a gateway for women, girls, low-income kids, and minorities of all stripes who are under-represented in our community to get into the web industry (see also #2 in this post).

My first week back at Automattic (starting Monday) I will be doing a week’s rotation on wordpress.com support with my team, but will then be jumping into a new role focused on our contributor community. It will involve a lot of projects, but one of the first will be aimed at increasing diversity in the contributor groups, starting with the gender gap. These efforts will all happen under the aegis of the new Community Outreach contributor group, so if you are interested in working on this with me (and Andrea Rennick, and Amy Hendrix, and Cátia Kitahara, etc), please join us! I’ve got a giant list of projects that I’d like us to tackle in the new year, and we’ll need people to help make things happen.

But what about core? And other stuff? I’m reserving Wednesdays to do design so I don’t get rusty. These “office hours” can be used by the core team to have me look at something, or by an Automattic team. Otherwise, I’ll use that day to work on designs to improve areas of the WordPress.org site to help with our goals, and/or tools to help us get things done.

So that’s the plan.

What do you think?

Forking, Woo, Free Agency, Automattic, and Me: Or, a Simple Comment that Became a Really Long Post

I started writing this as a comment on Mika’s post on The Morality of Forking, but I think if you start to pass two paragraphs, it’s time to write a post instead. So here it is.

Open source (and specifically WordPress) developers have a lot of options. When Daniel Pink wrote Free Agent Nation back in 2002, the idea that people could just go from good opportunity to better opportunity for no reason other than wanting to (more money/flexibility/peanut butter cups/new challenges/location/people/whatever) was still pretty revolutionary. These days, in our community, it’s the norm. Netflix has a good presentation on how to keep the employees you value. If people feel valued, they don’t leave. We accept less money, shitty hours, and even snotty customers when we feel good about we’re doing. Just look at any startup or non-profit job.

I have not been following the Woo/Jigo thing at all (WCSF and 3.3 have kept me busy lately), but if the description in Mika’s article is accurate about the steps that were taken, I don’t think Woo pulled a dick move at all. I’m the first to hop into the forums (in ninja mode, as Mika says) and tell off someone who wants to redistribute a paid plugin for free without adding any value to it — I do the whole legal-but-a-dick-move spiel. In this case, though, it sounds like they tried to do the right thing.

E-commerce and WordPress seem like such a natural fit, and yet nothing out there is great. Period. I love all the guys who develop these plugins (and I’ve tried most of them) but without exception there are always issues. Spaghetti code, bad UI, weak features… e-commerce plugins have seemed to have some kind of inverse version of the project triangle forever.

Will forking Jigoshop and hiring the developers who got it to its current state catapult Woo to the exalted position of “the ones who got it right”? Maybe. And if that happens then Jigowatt will be super bummed. Maybe not, though. Maybe Jigowatt’s vision is better and they’ll wind up with new developers who share that vision and they’ll come out on top after all. And if Woo just wanted to fork something, they might have been better off forking Shopp — it has a more consistent UI, less complex code, and better reporting. Then again, Jigoshop creates fewer tables and uses custom post types. Hm, but WP e-Commerce also uses CPTs, has way better reporting, and creates fewer tables than Shopp. This is the problem — everyone is doing something better than the others, but no one is hitting all the targets yet.* Presumably Woo chose Jigoshop because they thought it was the best option for a starting point. Either way, whoever gets there first will win the hearts of the community and a ton of new business. (Side note: this is why I think a core commerce plugin that sets up how the WP core developers would recommend doing it and that independent devs could both contribute to and build on top of would be phenomenal and is actually the right answer.)

So why take the developers? Obviously they liked their work, if they were trying to buy it. At Automattic, when we’ve acquired a product/company, it’s always been about the team that made the product more than the product itself. Isn’t that kind of the underlying ethos behind most of the open source models that are successful (both as purveyor and as buyer): don’t pay for code, pay for people?

So I don’t think it was dick move. Good developers/employees are a hot commodity, and you need to give them something they don’t want to lose if you want them to stick around. If Woo looked better to them, it’s none of our business — that’s a decision for them and their families. The devs shouldn’t be judged for deciding to take a new opportunity, and Woo shouldn’t be judged for offering one. It’s not as if they hadn’t made their interest pretty plain, if there had already been acquisition discussions — it’s not the same as secretly trying to poach employees from friends/partners/fellow businesses while pretending to have no interest in them (which would be a total dick move). If Woo doesn’t deliver on whatever promise they’re banking on, the devs will find another opportunity. That’s how it works.

I reviewed Free Agent Nation for the now-defunct New Architect magazine (which had just changed its name from Web Techniques) in 2002 and noted that it resonated with me because I averaged a new job a year as I moved from opportunity to opportunity once the current one stopped being good enough to keep me around. When Matt hired me for Automattic, during the conversation about salary I said I didn’t give a crap about stock options because I’d never stayed at a job long enough for them to matter. We also agreed on an unofficial “easy out clause” that would protect our friendship for the inevitable day when I left after the challenge was gone, got sick of the people, or just plain felt like a change and decided to either go to grad school or run off and be a baker in a beachside cafe in Mexico (or he got sick of me), which was estimated to occur within or around the one-year mark.

Three years later, I’m still at Automattic and am not looking. I have never stayed at one job this long. EVER. It’s not money — though Automattic salaries are competitive, I made more at both of my last two jobs. I don’t run out of challenges, I respect both my co-workers and the company leadership, and Automattic works hard to make sure my work environment is awesome. They even make me take days off when I work too hard. I mean, come on.

Mika mentioned in her post that Nacin almost went to Woo before Matt “snatched him up.” She forgot to mention that John James Jacoby was consulting on WP e-Commerce for Instinct before Matt snapped him up, too. Dan has made a few comments of friendly resentment to me about this, but J-trip had already applied to Automattic when he started consulting for them and had informed Dan of this in advance — I can’t help it if sometimes our hiring process takes a long time (we like to be really sure the fit is perfect, which is part of why we have such low turnover). Even if J-trip hadn’t applied to us first, though, would it have been wrong to hire someone who wanted to be here? We should not be putting the success of companies before the happiness of the people who work for them (and make them successful in the first place). Corporations are not people, as much as the US Congress would like to believe it, and in our community, a company name is only as good as the people behind it. I want every WordPress developer/worker to be ultra happy, wherever that may be. I would believe this even if it meant Woo hiring away every single person from Automattic, and they are welcome to try (though Matt it would probably think it was rude to poach without giving us a heads up for the sake of the relationship, and he’d be right).** Who knows, a maybe a year from now Jigowatt will nab people from Woo. Or StudioPress will swipe iThemes guys. Or WebDev Studios will hire CubicTwo peeps. You get the picture. The thing is, if people are “swipable,” they’re not where they belong anyway, so no one should begrudge a change.

By the way? Automattic is totally hiring badass developers and designers and happiness engineers (wordpress.com support), so if you are one of these and need a new challenge, you should apply. The team I lead, the dot org team, is a group of people that are donated to the open source project: me, Ryan Boren, Andrew Ozz, Daryl Koopersmith, Chelsea Otakan, and Andrea Middleton. Wouldn’t you like to be the next name on that list? I need a developer or two. Must love the GPL, coding according to WP standards, decisions instead of options, Doctor Who/Dr. Horrible/The Guild/Firefly/Portlandia/Buffy/Torchwood (more the old one)/Misfits/Eureka/Warehouse 13, kittehs, standardization, accessibility, watermelon mimosas, turtles (sea variety), Words with Friends/Scrabble/Bendywords, steampunk/paranormal novels, and good food and booze. A couple of those are negotiable. Well, maybe. Think you’re good enough and cool enough? You might be right! Apply.

* Credit where credit is due: John James Jacoby recently did a review of the top shopping cart/ticketing plugins at my request. We’ll be releasing his findings soon.

** Fair warning if you’re going to try to poach from Automattic all sneaky-like instead of right out in the open: we love each other here, and we’re likely to immediately turn around and tell the rest of the company. Better to be up front and transparent and just say, “We really need someone like so-and-so and would love to have them on our team if they’re interested,” than to skulk around like a headhunter. When employees are unhappy, skulking works. Not so much with us. We will mock you on our internal blogs. :)