Go forward. Move ahead.

Devo_Jocko_Homo_MongoloidThis week was my first week away from Event Espresso.

What’s that you say? You didn’t know I was leaving? Well, it wasn’t an easy decision.

Pros of working at Event Espresso

Some of the things I loved about working with Event Espresso was being part of a great team, being able to contribute to development, and being able to help shape the direction of the plugin and the business. These are all good things.

When I first started working with Event Espresso, it was that or going back to work at Whole Foods. Business was slow, Museum Themes hadn’t taken off, and things were getting rough. Event Espresso was one of the few opportunities that allowed me to work at home and get a regular paycheck, and for that it was great and I jumped at the opportunity. Over the course of 2 years, I learned the business as well as the plugin, and was able to help steer the direction (or at least offer my suggestions) for both.

Cons of working at Event Espresso

Here’s the dilemma: my freelance web development business was still slow and Museum Themes still hadn’t taken off. I’d been with Event Espresso for 2 years and I always said that I’d be able to work on that stuff on the side, but it never happened. I was always working at Event Espresso, working long hours, constantly in front of the computer, and I was watching my life pass me by. On the one hand, I was a valued member of the team, on the other I was cranky all the time from the stress of doing support and of having half a dozen different things that needed to get done RTFN on any given day and I was passing up potential clients because I just didn’t have enough time.

I tried a number of things. I tried having one day a week where I did client work or work on Museum Themes. That sort of worked — in that I could do one or the other — but if I had both, Museum Themes got pushed (once again) to the bottom of the pile. I started cutting my hours back so I was only working about 20 hours a week. That helped me get through my most recent course for Pluralsight, but, again, everything else got pushed to the bottom of the pile and I was still cranky and stressed.

Work smarter

In short, I’ve been working really freaking hard for the last couple years and I feel like I don’t have a lot to show for it. Certainly my sanity and my availability to my family has been worse for the wear. When Megan from Pluralsight approached me last fall at WordCamp SLC, I was skeptical. I wasn’t sure if this was a one-off deal or if it would be something I could do as a steady gig. And I knew nothing about the company, their background, where they came from, how legit they were. I didn’t know if doing Pluralsight courses would pay off, if it would be worth it, if I would just be working really hard and nothing would really come of it.

But when I finished that first course, we celebrated with a bottle of champagne. And when that first royalty check came I could see that, yeah, this is something that could be a real thing.

It’s not that doing a course isn’t hard work — it is. It’s really hard, actually. It involves creativity and creativity doesn’t grow on trees. But one of the differences is that I need to know the stuff I’m teaching and that means I need to be constantly learning and experimenting — things I want to be doing anyway but previously didn’t have enough time. Sure enough, as I was finishing off my last course, I started getting ideas of what my next course would be (my next two courses, actually). Doing a course for Pluralsight means I actually need to take time away to do other things, which helps me stay fresh and motivated and then inspires creativity when I start working on something that I can then turn into a course (or a part of a course).

Even if I run out of WordPress-related ideas (which I don’t see happening for a while), the WordPress development cycle is about one major release every six months, so at the very least, I could do a course every six months covering what’s new.

I’ll still be involved with Event Espresso for the foreseeable future. Right now I’m working on doing use case articles for them and I expect to still be a part of the Espresso Bar hangouts once a month. I’ve had a week away and I feel like it will be an adjustment, but I’ve gotten a lot of stuff done, lined up some possible client work, and I’ve started working on my next Pluralsight course. Best of all, though, I feel like I’ve been much less cranky. All in all, I think it’s been a good week.

New gig

As of today, I have a new gig.

The longer story is that things have been slow in the web design front.  My going theory is that the industry — especially given the economy; that great excuse we’ve been using for everything from health care to what store we shop at — is moving toward customizing existing solutions (say, modifying a premium theme for WordPress — a free software application) rather than completely custom websites.  To be fair, the industry has a point.  WordPress is getting increasingly more robust and easy to use, there’s less and less of a reason to have someone else set it up for you if you know you’re going to use it anyway, especially when your webhost has a little button that says “click here to install WordPress” (of course, this option throws all security out the window, but it’s easy to stick your fingers in your ears and say “la la la la la la la” on that point since it isn’t something that has an observable effect…until your WP database is hacked).

This past summer has been particularly hard and we’re still trying to recover.  Museum Themes is slowly picking up — our sales are increasing every day — but the best it’s able to do at this point is keep itself afloat.  It doesn’t, for example, pay me to build new themes for it, so Museum Themes development gets thrown along the wayside in favor of paid work (when we have it).  And we’ve been needing more of that.

I started looking for a job.  At first, I was mostly just looking to get a job in the Specialty department at Whole Foods again — especially with them opening a new store in a week.  This time, I’d work (or try to get) a full-time position, and focus on Museum Themes on my off-days, do client work as needed, but scale that back quite a bit and put the expected completion times out further.  But that didn’t happen.  (The new store only had 2 positions available in Specialty and I was sort of — naively, perhaps — adamant that that was where I wanted to be.  The Great Salt Lake Whole Foods Store Shuffle, which will undoubtedly occur once the new store opens and everyone starts vying to get into that store, hasn’t happened yet, and probably won’t for a couple months.  Meantime, we need something sooner.)  So, I went to my old standby jobs of helpdesk/tech support and web design.  I actually found a couple (not very promising) web design jobs, but mostly was finding tech support stuff.  Which, of course, I have years of experience doing above and beyond being the guy that rips apart computers and puts them back together again.  I actually had a pretty good week for interviews last week.  And yesterday morning, I absolutely nailed an interview to be a Counter Intelligence Agent at Best Buy’s Geek Squad.  (It’s just, you know, Best Buy.)

But sometime at the end of last week, Event Espresso — those guys I met at WordCamp last year that do an event registration plugin that’s astoundingly well-built and is doing really well, having been covered on WP Candy a couple of times and in conjunction with their campaign to give all WordCamps a free Event Espresso license to prevent them from having to spend ridiculous amounts of money using Eventbrite instead — created a job board, and posted a couple internal jobs which they then tweeted about; namely, Web Designer, WordPress programmer, and technical support.  All three of which I could conceivably be doing.  I applied immediately.

Yesterday, I met with Garth and Seth — the first time I’ve seen them in person since WCUT, though I watched Seth on his video interview with WPCandy — and we had a meeting at a Wendy’s.  (Oddly enough, this isn’t the first time I’ve had a business meeting at a Wendy’s.  Just a different Wendy’s.)  At the end of the hour, my user account on the Event Espresso support forums was upgraded and shortly thereafter I had an official Event Espresso email address and spot on their About page.

This is an excellent opportunity.  First of all, I get to continue to work at home and more or less do the same stuff I’ve been doing.  I’ll need to buckle down and I created a hard schedule for my weekdays so that I have enough time for everything and can — hopefully — manage my time and be more productive with it.  This means no Twitter during working hours, sorry @Twitter.  Secondly, I’m doing the same stuff I was already applying to anyway.  Third, this gives me an opportunity to really dig into Event Espresso and learn the code, which is something I’ve been wanting to do since agreeing at WordCamp to develop some Event Espresso themes.  Fourth, though the support job is part time, they get non-support related requests for customizations — stuff I’ve been doing a lot of already — and that’s stuff I could potentially pick up as well.  Lastly, these guys are local and they’re cool guys.  It’s good for everyone because we can actually meet in real life if we wanted/needed to and because we already knew each other.  It also makes things a lot easier with the aforementioned theme idea, since I’m now actually affiliated with them.

So, I’m pretty excited and I’m looking forward to it.

WordCamp Utah 2010 — a belated recap

One of the things I heard at WordCamp Utah was that it’s not what you learn at WordCamp as much as the research and stuff you learn once you get home and start trying all this stuff out.  In that sense, I don’t think I actually left WordCamp at approximately 5:30 Saturday evening a few weeks ago.  Or, at least, WordCamp hasn’t left me.

This being my first WordCamp, I had to come to a few realizations that weren’t altogether surprising, but they were necessary.  One important one was that there’s two types of information you get from WordCamp: there’s the stuff you learn in the sessions you go to, and there’s everything else, including fragments of conversations, bits of code peeked at over someone’s shoulder, and rubbing elbows with someone who just happens to have an awesome event registration plugin.  Learning isn’t confined to a classroom, and WordCamp isn’t just about the seminars.  In Matt‘s town hall session, he said

If I could design the perfect introduction to WordPress…it would be a WordCamp.

I don’t think he was talking just about what happened inside the lecture halls.

The first half of my day was spent at the Geek Genius Bar.  Those of us who had volunteered for the Genius Bar were asked to come a few minutes before registration officially opened.  I made it — barely — only to find that I had no idea where to go.  I found my way to the Skaggs Biology Building easily enough (Google Maps being my friend), but once I got my badge, t-shirt, and obligatory swag (some of which was identical to the swag I had just received with my WordPress t-shirt and officially-signed certificate of being one of the three most important people in WordPress about a week before), there wasn’t any place already established for us geniuses to meet.  In fact, after passing the big guy with the purple hair and the 9Seeds shirt, I asked a couple of attendees if they were “geniuses” only to be greeted by resounding “uh, no!”‘s, to which I had to explain that I was (though I didn’t feel like it at the time), and as such, had no idea what I was supposed to be doing or where I was supposed to be.  Only later did I learn that said purple haired geek was Todd Huish from 9Seeds — who would be spending the bulk of the day manning the Genius Bar whether anyone else was joining him or not — as he started moving some chairs and a table that would serve as the Genius Bar.

There was no signage for anything — one of the things overlooked during planning that Joseph Scott — who organized the shindig — hadn’t gotten to — so I took it upon myself to print out some of my own from my analog tablet: a small notebook.  I spent much of that first half of the day hanging out with Todd and Seth Shoultes (who makes Event Espresso).  And, of course, one of the first questions we fielded made us all doubt our collective genius-hood, it being a complex programming challenge that didn’t really have anything in particular to do with WordPress other than that the person involved (who was a spokesman for “a friend”) wanted to use WordPress for this site.  That was, thankfully, the most difficult and least WordPress-related question we had to take (at least while I was sitting there).  Which leads me to another revelation I had: I know an awful lot about WordPress Mu/Multisite.  During the course of my tenure at the Genius Bar, I also met Josh Strebel of Page.ly.  I checked Page.ly out when @WordCampUtah retweeted that they’d be there, and they’re doing something really cool.  WordPress-specific, managed hosting, so you don’t need to worry about how your site is running, you just need to have it.

Before lunch, Matt Mullenweg did his thing, and for WordCamp Utah, his thing was a town hall forum wherin he answered questions that led to topics ranging from the GPL to Kanye West’s Twitter account to the machinations of GooVerizonigle.  I was happy that it wasn’t just his keynote at the SF WordCamp in May (which can be seen on WordPress.tv and partially inspired me to attend WordCamp in the first place), but I was a little disappointed that it wasn’t something more substantial.  I love Matt’s talks, I’ve listened to a few and follow his blog.  Of course, that means I have a pretty good idea of what he’s going to say about any particular topic, so I ultimately decided that it was better this way.

Lunch.  So, also on the Utah WordCamp site, Joseph announced that BlueHost was footing the bill for lunch and that it was going to be from Sugarhouse Barbecue.  Great, says the vegetarian, looks like I need to bring my own lunch.  While I wasn’t overly annoyed at the choice of entrees — I’ve been veggie long enough not to assume that people will take it into consideration and find alternative sources of nutrition, or at least things resembling nutrition — I was annoyed when it got closer to lunch hour and I had more than one “oh come on, you know you’re just here for the free barbecue” comment tossed at me.  Um.  Actually.  No.  And while I wasn’t overly surprised that there wasn’t, at least, a fish option (heaven forbid a veggie-burger), I couldn’t help but be the least bit disappointed with my lunch of potato salad and cole slaw.  At least it was good potato salad.  And a cookie.  A really big cookie.  And, despite the fact that I’d sworn off soda earlier in the week, someone managed to dig out the last Coke from the cooler, so all in all, it could have been worse.  And anyway, the best part of lunch wasn’t the food.

I hung out with Todd, who’s an extremely cool guy, and we talked about Thai food and pizza and probably other stuff, too, although the food stuff seems to stand out most in my memory for some reason (possibly subconsciously wishing it was that food on my styrofoam plate, rather than what I had).  Later, while waiting for the Will it Blend? session, I started eavesdropping, then deliberately cut into a discussion and show-and-tell of the new WordPress feature to 3.0, custom post types.  Custom post types sounded like a cool idea, but I had no idea how to actually use it.  I got to see how John Hawkins (also of 9Seeds) was using it for the WordCamp Las Vegas site, and it’s astoundingly cool.  Not just cool, but useful.  The first thing that comes to mind is the ability to design an e-commerce site strictly by using custom post types — no plugins, special themes, or extra software required.  Boo yah.  Throughout the day (and before even going to WordCamp Utah), I heard various mentions of “child themes” which was a concept I sort of filed away for later.  If you’ve seen my tweets on @ArcanePalette recently, you’ll know that it’s now my new most favoritest thing about the new WordPress, and we’re planning on doing a lot in the child theme department in the coming months.

The answer to the question Will it Blend? was, well, no, actually.  WordPress defeated the blender.  Sort of.  “WordPress” was being represented by a USB thumb drive of WP code and a coffee mug with the WordPress logo.  The audience insisted that the mug go right-side-up and that was the undoing of the blending, since it got stuck and was unable to get caught by the blade.  Tom Dickson eventually made an executive veto and flipped the mug, which was duly turned into porcelain dust.  But before all that we got to hear about the no-budget viral marketing campaign of Will it Blend? Basically, BlendTec was this company (K-Tec, originally) that had awesome products, and assumed if you had an awesome product, so come the sales.  Obviously no one in their company was a marketing guy.  So they started this Will it Blend? campaign of throwing stuff into their blender and a few million views later, online sales (for a really freaking expensive blender, mind you) are up 700%.  It was kind of fascinating, and I probably wouldn’t have gone if it weren’t for the fact that it was pretty much assumed that everyone was going to be in the room.

Immediately following that was John Hawkins’ plugin development session (which you can actually see here, although it’s from Portland).  Another one I wasn’t planning on going to, but since I had just watched him blow my mind with custom post types, I figured I’d drop in.  I haven’t ventured into plugin development.  I’m a visual guy, not a code guy (although increasingly I’m getting more and more dirty with code).  So building plugins wasn’t something I thought I’d really have any reason to do.  That was extinguished when he opened with how he got into plugin development.  See, he likes to change his theme all the freaking time, and the annoying thing about that is that if you have a lot of custom code, that means having redo all that stuff all over again.  (At this point my ears perk up — this sounds very familiar.)  You can get around that by building plugins that handle all that extra functionality.  You know, the rest of the session, it almost didn’t matter (I mean, sure, I got to see how easy it is, and all you need is the header information and there are a couple really cool development environments that aren’t Dreamweaver that you can use — sorry, I’m still hooked on Dreamweaver) because that first 5 minutes was really all I needed.  That and a couple of links that I duly took home and looked up, building 5 separate plugins to handle the custom code and added stuff that I throw into this site.  (Note: expect this space to change its appearance on a  more regular basis — like every time we release a new Museum Theme.)

Following that was the BuddyPress session, which I was planning on attending.  However, I got less out of this than I had hoped because it was really more about why you should use BuddyPress than stuff you could do within it (although I did learn about a BuddyPress plugin that I’m planning on adding to Museum Themes to automatically sign people who buy a theme up for the Support Forum, rather than making them have to join the group first).  The last sessions of the day were one on theme development, and Josh Strebel’s presentation on Collaboration over Competition.  I stuck around for Josh’s presentation partially out of laziness (it was in the same room, after all), partially because the Event Espresso guys were there, partially because I already know an awful lot about theme development.  Now, as John pointed out earlier in the day, you always learn something, and you might think a geeky developer-type like him would be beyond picking up new information in a session about ‘the loop’, but if you thought that  you’d be wrong.  Still, I stuck around because I was kind of sort of trying to get on Josh’s good side (I not-so-secretly wanted to see if we could get Museum Themes offered alongside StudioPressWooThemes and Press75).

I have a few things to say about his presentation.  Now the main point of the presentation I get, and I’m right there.  Just because we’re competing in the same market doesn’t mean we have to be head-to-head — it doesn’t mean we can’t still work together on the same projects or help each other out.  He uses the example of the 10,000+ plugins in the official WordPress plugin repository.  More than 10,000 plugins!  And while Matt uses this as evidence of a great, thriving community, Josh points out that he found 5 separate plugins 111 plugins all for the new Twitter tweet button.  Couldn’t those 5 111(!!) people work together and build 1 really cool tweet button plugin, rather than 5 111(!!) kind of crappy (and a few possibly mediocre) ones?  That’s the gyst, and here’s my beef: in a perfect world, where all things are equal, and all coders, designers and hackers are equal, sure, we can spread the load, we can all work together to build one really amazing platform for…something.  But competition breeds innovation.  Competition breeds originality.  So there’s 5 tweet buttons or 15 premium theme developers, sure we could work together and have 1 tweet button, 1 premium theme, but in that game, the one with the loudest voice rules.  It eliminates the possibility for something really interesting and innovative.  In fact, it’s kind of the polar opposite of our mission with Museum Themes.  See, the thing about the premium WordPress theme market is they’re all trying to be the best thing for you.  Every single one of you (or, alternately, all twelve of you if we’re talking about the people who actually read this blog).  We don’t care what everybody wants, in fact, we reject what everybody wants.  We design based on what we want, with the assumption that there’s gotta be people out there with similar tastes, similar values, and similar styles.  In short, we design for individuals rather than masses.  So there, I said it.  And you know what?  I am collaborating.  Right now.  I added a fix to some bugs I found in Event Espresso Lite (aka Advanced Event Registration), and I’m working with the Event Espresso peeps to build some event registration-based themes along the lines of a real ticketing site (see: 24tix.com, ArtTix, SmithsTix.com, find your local equivalents).

And that brings us to the final point of WordCamp — possibly the most important one.  It’s not about any of the shit that happens at WordCamp.  It’s about people.  It’s about ideas.  It’s about what you do when you leave WordCamp.  (I think I said that one already.)  And it’s weird and also pretty cool to have people on Twitter that I follow now that I actually know in real life.  It’s a lot cooler than, say, being the guy who told Matt where the bathroom was (yeah, that was me, too).