Quick Overview

You’ve decided that version control is where it’s at, and are ready to give this GIT thing a spin. But what happens now? You head to GIT Immersion and learn by doing, that’s what.

Image based on film_strip by liladepo, CC-BY-2.0.

How did you first get into web development, and at what point did WordPress enter the picture?

I first got into web development in 2001 when I was working for the Labour Party — I was asked to join the editing team for their general election site and I took the opportunity to learn some HTML while I was at it. A while after this I designed websites for learners when working in management development, which prompted me to consider going into web design and development full time. I set myself up as a sole trader in February 2010 and formed my company, Compass Design, in September of that year. By then I was starting to develop more and more sites in WordPress for clients who wanted to be able to update and manage their own site. By 2011, I was working exclusively with WordPress.

As the head of Compass Design, you’ve chosen to specialize in mobile and responsive WordPress design. Where did the idea come from to focus on this area specifically, and has specializing helped set Compass Design apart from the pack in terms of positioning and winning clients?

To be honest I can’t really remember! I know I had a client in 2010 who wanted a mobile version of their site — this was before responsive design had taken off, so we used a plugin. After that I started taking an interest in mobile design and development because I was increasingly using my own phone to access the internet. I gave my first talk on the topic at WordCampUK in July 2011 after which it seemed to make sense to develop this area and focus on building responsive sites for clients. I was lucky that this new technique was emerging as my business was growing, as everyone was in the same boat and the more established agencies didn’t have any more experience in responsive design than I did — in fact, not having years of doing things another way gave me a bit of an advantage in some ways.

I think it has given me a slight edge, as I’ve definitely picked up clients who’ve seen my writing and that gives them confidence in my ability before they even speak to me. But as with any business, what wins me clients (exclusively referrals, these days) is providing a great service and taking time to understand what my clients’ real needs are.

How do you typically convince would-be clients that they need to bring their site into the mobile age, and do you ever encounter any resistance to the idea?

It helps that I don’t charge extra for making a site responsive, I see it as part of my offer, so it’s included. I find that if I ask a client to hand me their phone and point the browser at a responsive site I’ve developed, that convinces them pretty fast. Many clients don’t think they need a responsive site until they see it, and if they’re ambivalent at first, when they hold their own site in their hand, there’s always a ‘wow’ moment. So I’ve been lucky not to encounter any resistance!

Where do you see designer-developers going wrong most often in their approach or implementation of responsive design, and what pitfalls should they be most mindful of avoiding?

I don’t think that there are examples of people ‘going wrong’ as such, but I do think that the way responsive design is approached is evolving and designers and developers need to keep up with that. For example, when we started writing media queries, they were always based on the iPhone’s dimensions, and after a while that expanded to accommodate iPads and other large tablets. But now there are so many devices of different sizes that the breakpoints for media queries should be set at the screen width where the design breaks, not at the width of one specific device.

However I do think there’s one area where designers of mobile-specific sites (as against responsive sites) get it wrong, and that’s when they don’t make all of the desktop content available to mobile users. Some big brands still make that mistake and it drives me nuts.

You’re the author of WordPress Mobile Development Beginner’s Guide, WordPress Theme Development Beginner’s Guide, the forthcoming WordPress: Pushing the Limits, and also have a novel on the back burner. What part has writing played in your life, and how has it dovetailed with the knowledge and experience you’ve built through your design-development work?

I’ve always loved writing. At school I loved writing stories and mini-novels and I’ve planned and started quite a few novels in my time; this is the first one I’ve actually finished, and someday I hope to see it published. In just about every job I’ve ever held, I’ve spent a lot of time writing, partly because colleagues have recognized that it’s something I do well. Now I’ve had two WordPress books published, another due out in June and have written articles for a variety of online journals. I’ve been incredibly lucky to be able to combine my work designing and developing websites with writing, and can only thank Packt for approaching me with the proposal for my mobile WordPress book which kicked it all off.

Tell us a bit more about your Mobile Development book, and who would benefit from reading it.

The book is aimed at people who’ve got some experience using WordPress to build websites, know their way around the admin and can maybe write a simple theme, but have little or no experience of mobile development. It takes them through the process of making a desktop site mobile-friendly, looking at plugins, media queries, and web apps, and has content that’s relevant for developers who don’t work in WordPress but want to learn about responsive design.

Are there any cases where a designer-developer shouldn’t be putting responsive design best practices to use in 2013?

There are some scenarios where a site’s users have very different needs on different platforms, in which case I would develop separate themes for mobile and desktop. But this should be based on mobile/desktop users having a defined need to complete different processes, not on the needs of the site owner to speed the site up, save money or avoid the complexities of making an existing site responsive. In 90% or more of cases, responsive design is the way to go, in my humble opinion!

Where would you point a reasonably new WordPress designer-developer looking to get up to speed with responsive and mobile friendly design, and are there any essential shortcuts, plugins, or other helping hands they should keep in mind?

The default WordPress theme, Twenty Twelve, is responsive, and picking that apart can help developers understand how a responsive theme works. However I think the basics of responsive design are independent of any CMS so I would encourage theme developers to read Responsive Web Design by Ethan Marcotte, which will show them how to write media queries and create a fluid layout. Another great but not so well-known book is Stunning CSS3 by Zoe Mickley Gillenwater, which I read before Ethan’s book and which taught me a lot about responsive design.

As far as essential plugins are concerned, the three I use the most are Responsive Select Menus, which turns navigation menus into select boxes, Mobble, which lets you send different content to different devices using conditional tags, and WP Responsive Images, a really clever plugin that automatically sends smaller image files to mobile devices without relying on user agent sniffing.

You’ve also presented on the case for creating WordPress-powered web apps. What makes WordPress a good basis for a web app, and are there any key tweaks or streamlining measures a designer-developer should keep in mind when adapting WordPress to web app scenarios?

The main reason I would recommend WordPress for web apps (or many other CMSes, for that matter), is the fact that you can use a separate theme for your web app while still having all of your content in one place in the database. This means that any overlapping content between the main site and the web app doesn’t need to be duplicated. It also makes it easy to let users switch to the ‘main’ site on mobile devices and see a responsive site as against a shrunken version of the desktop site. In addition to this, there are loads of WordPress plugins out there providing the kind of functionality web apps require: ecommerce, mapping, forms, events management, and much more.

How well does WordPress work out of the box as a mobile/multi-device platform, and are there any improvements you’d like to see in future versions to better solve the challenges that the mobile web presents?

WordPress is pretty good as a multi-device platform, given that it comes with a default theme that’s fully responsive. For the front end, I think the main area for improvement is around image management. While there are plugins that deliver smaller image files to mobile devices, I’d like to see WordPress’ media management integrate with the proposed new picture element to give finer control over the way images are used and displayed. This is a way off yet, and is reliant on the W3C developing the proposed element further.

For the admin system, I’d like to see it being easier to manage a WordPress site on an iPad. There’s a great WordPress app for smaller mobile devices, but on the iPad I tend to use the browser to interact with WordPress and there are some aspects of that that don’t play nicely. I know that the community of WordPress core developers are working on these though, which is great news.

Finally, you’ve recently written two books that focus on users at two polar extremes of familiarity with WordPress. What challenges were there in communicating about WordPress for beginners versus seasoned veterans looking to push the envelope of what’s possible with WordPress?

Working on these two books at the same time has been a real challenge. One day I’m writing guidance for novice WordPress developers to help them build their first theme, and the next I’m delving into PHP to find ways advanced users can push WordPress further for complex client projects. The first has been enjoyable because it allowed me to recap my own theme development skills and ensure they were up to date, while the second has been a great learning experience for me experimenting with aspects of WordPress and investigating techniques developers are using to push WordPress way beyond its original function as a blogging platform. This book, WordPress: Pushing the Limits, has been my greatest professional challenge to date (not least because of the tight writing deadlines) but also one of the most enjoyable things I’ve done and it’s inspired me to push further with the work I do for clients.

How did you first get involved with WordPress, and what brought it into your life?

So I had been dabbling with open source platforms in high school around 2006. Mostly WordPress, and a few others I can’t bear to mention. Although I didn’t really get involved with WordPress until early 2009, while studying Computer Science at Rutgers University, when I had taken an entry level programming job for an ad I found on Craigslist.

The job description wasn’t WordPress specific but mentioned open source solutions which was something I was interested in. Within a week of applying, I interviewed with Brad Williams, CEO and Co-Founder of WebDevStudios, and got the job as their first developer hire.

From that moment on my WordPress career was kicked into overdrive. At WebDevStudios, not only was I involved with building really cool things for clients with WordPress, I was releasing plugins on the WP.org plugin respository and heavily involved with the WP community both helping out with meetups in the area and attending various WordCamps. I actually attended seven WordCamps across the country from 2009 and 2010: Mid Atlantic ’09, Chicago ’09, New York ’09, Boston ’10, Miami ’10, San Francisco ’10, and New York ’10.

These first two years have definitely shaped who I am today. I learned a lot in a short period of time and made a lot of really good friends along the way.

You’ve worked as a developer with WebDevStudios and more recently (up to the present) as a Support Ninja at WooThemes. What did the one bring to the other, and how are they most different?

I actually wrote a blog post around this over at WP Realm titled What Makes a Great WordPress Support Specialist.

In the article I write about my previous experience as a developer and involvement in the WordPress community was a huge benefit to my transition into the support world:

“…having a technical background and general knowledge of WordPress coding standards and best practices is a HUGE win. This has really helped me. With a stronger background in WordPress development and involvement in the community, I’m able to not only provide knowledgeable answers but am confident that they are up to par with WordPress coding standards. In other words, done the right way.”

With that said, being strictly support I feel that I’ve fallen out of the loop a bit and am looking for ways to stay involved and keep my WordPress and coding skills fresh and up to date. That’s something I’d never want to let go and am currently involved with developing a few plugins and projects on the side.

At WooThemes you’re a Support Ninja. What interested you most about taking on the job, how have you made it your own, and what’s surprised you most about what it entails?

Short answer is that I’m passionate about helping people and love WordPress so it’s a perfect fit.

While working at WebDevStudios we had Support & Maintenance packages for clients which I also managed alongside client development. It wasn’t really the same thing as what I’m currently doing at WooThemes but I learned that I enjoyed helping users with WordPress and when I saw the opening at WooThemes I knew it was the job for me.

As of April 1, I’ve been at WooThemes officially for a year supporting our customers. I think that’s what surprises me the most. Not because I’d expect to be somewhere else but because I still love what I do.

Most people may view support as a boring, tedious, repetitive task but I’ve learned to really enjoy it. Each and every day has it’s new challenges and obstacles for me to take on. Not only am I solving problems and pointing people in the right direction, I’m also learning things on the way so it’s really a win win. Most of all, I strive to deliver happiness. Who doesn’t love that?

I actually gave a talk about this earlier this year at WordCamp Norway titled Help Yourself by Helping Others, which you can find on WordPress tv. If you can deliver happiness in every aspect of your support you’ll only benefit and this is something we try to do at WooThemes.

You work remotely for WooThemes from Norway. What tips would you give newbs to the whole work-from-home thing, and what do you wish you’d known when you first started working remotely?

My biggest advice to those who are new to working remotely would be to make a work schedule and try stick to it. If you aren’t strict to this you’ll easily find yourself working all the time so try to have a healthy work-life balance. This also ties into what I would have liked to have known when I first started working remotely. I’ve just started to find a nice balance.

Also, I definitely miss the social aspect of working in an office but yearly trips where you can meet your colleagues, like our annual WooTrip. Also, meetups and WordCamps in the WP community definitely make up for it. It’s definitely not for everyone but I wouldn’t trade it for anything. Not everyone can work from home, the local coffee shop, or even from an airplane which I’ve now done a few times. Incredible!

At what point does a WP outfit need a dedicated support person (or people), and what can bootstrappers just getting started do to make their support at least as good as it can be in the meantime?

Right away. Support is easily the most important aspect of your business, even if you are just starting out. You obviously need to have a product or service, but definitely don’t overlook support or throw it under the bus.

Again, don’t just do customer service or support, focus on serving happiness to your users/customers and you’ll be doing things right.

Conversely, where do you see people going wrong with customer service, and what are the consequences of that?

The biggest issue I see is people have a wrong view around support. I bet most people even cringe when they hear the word. Will you have horrible experiences and miserable clients? Of course, but let it go and focus on the users and customers who actually appreciate your help.

Here’s a quote from Mark Forrester, WooThemes co-founder, that really hits the nail on the head: “Customer support is the opportunity to convert a disgruntled customer into a loyal product evangelist by over-delivering and creating a memorable human connection with a digital brand.”

Remember, support isn’t a bad thing or a headache for your company. It should always be viewed as an opportunity to benefit.

You’re also the author of some awesome plugins. Which are you proudest of, and what itch were you trying to scratch with it?

I’m definitely most proud of CollabPress. A plugin I released in January of 2010 which, at the time, was BaseCamp on WordPress. There was a need for a project management plugin in the WP community and I decided to make something. We used it at WebDevStudios internally and a few others were as well. I think most successful plugins are those you can both use and benefit from yourself and release to the public as well. Open source, it’s a beautiful thing.

Although I can’t take all the credit. CollabPress 1.0 was a complete rewrite, once custom post types were introduced in WordPress, and Brad Williams, Boone, Eric Andrew Lewis and Christopher Cochran have put a lot of hard work into it as well.

Eric is actually the lead for v1.3, which released last week, and it’s a complete UI overhaul. I love the project and look forward to it’s bright future. You should definitely check it out.

Which three essential plugins would you recommend to WordPress designers and developers up against deadlines, but trying to ensure that their client’s site doesn’t get borked within a few weeks of installing them?

Tough question!

With WordPress being used for so many different types of sites even picking three plugins is difficult these days. Here’s three, you’ve definitely heard of and are most likely already using, I’d use on almost every setup:

1. Jetpack — While I usually turn most of the features I don’t need off, Jetpack has a few great tools out of the box like stats, short URLs, easy embed, etc. I love it.
2. W3 Total Cache — Site speed and performance optimization is a must these days. W3 Total Cache is a great caching tool for your WordPress site. Speed up those load times!
3. WordPress SEO — I’m not an SEO guy, never have been and probably never will be, but it’s important for the success of your site and WordPress SEO does a great job optimizing your site to best SEO practices with WordPress.

What would you say are the three most important skills or characteristics of a kick-ass world-level support person?

A kick-ass world-level WordPress support specialist needs to:

1. Not only passionate about WordPress but also involved in the community and loves to give back wherever he/she can.
2. Be a “people person”, i.e., friendly and easy to communicate with and who can help even the most un-grateful person with a smile.
3. Have some sort of technical background & skills whether it be HTML/CSS, JS, and/or PHP. Knowledge of WordPress coding standards and best practices is a HUGE win.

from http://wprealm.com/blog/what-makes-a-great-wordpress-support-specialist/.

Last up, how important has your involvement in the WordPress community been to you and your career so far? How would you convince someone up against deadlines that giving something back to the community is worth their time?

It’s been everything and still is. WordPress is truly an amazing platform, it’s the best. But, I don’t believe the success of WordPress is directly related to the product itself. It’s the community that separates it from the rest.

Just last week I had the privilege of organizing an online WordPress event called WordSesh. WordSesh was 24 hours of live WordPress presentations. It was fully free and it’s one and only purpose was to teach people about WordPress. It had over 34 speakers, from all over the world, and with events like WordSesh, meetups and WordCamps I’m really proud to be a part of a community that always comes together to better WordPress.

If you aren’t involved in the community already you are missing so much. For starters, you could regularly attend a local WordPress Meetup, go to a WordCamp. And if there aren’t any near you, you could even look into starting your own like I did here in Norway. The connections you’ll make and knowledge you’ll learn are priceless and well worth your time.

I would also make sure to check out make.wordpress.org to see how you can give back to WordPress. It’s not always easy to find time in our busy schedules to give back. I wish I had more time to, but every little bit helps and let’s continue to make WordPress the most popular tool on the internet.

Quick Overview

Whether you totally missed the free 24-hour-streamathon of WordSesh, or just want to catch up on the infinite payload of WordPress wisdom shared by its participants, you’ll be pleased to know that the whole thing has been captured on YouTube for your viewing pleasure.

Image based on Words by Alby Headrick, CC-BY-2.0.

Quick Overview

WPShout kicked off in 2009 and has been bringing a range of free resources, insightful opinion pieces, and useful tutorials ever since. With pieces on everything from the economics of premium themes, to comparison pieces on WordPress hosting services, with a side order of free ebook, screencast tutorials and more besides, it’s well worth your time.

Image based on shout by Krista Baltroka, CC-BY-2.0.

Do you remember when you first encountered WordPress, and the point that you realized it was something you’d work with professionally?

I first remember hearing about WordPress in the mid-2000s, when a few friends at CUNY were doing some pioneering work with WPMu. I used WordPress a little around that time while teaching Ethics to undergraduates: I had them keep philosophy journals on public wordpress.com blogs, which allowed for better peer review. In 2009, I was asked by my friend Matt Gold to help out for a few hours a week on his CUNY Academic Commons project. CAC was built on WordPress and BuddyPress (then in beta), and needed someone with some real technical chops. Despite this fact, he asked me to help. I knew nothing about WordPress or PHP when I started (just a bit of HTML/CSS). Within a few months, I’d written and released my first plugin. Within a year and a half, I’d quit my job to do WordPress consulting and development full-time.

You’re a Lead Developer for BuddyPress. How did you get involved with it, and what itch was it scratching (or not quite scratching) for you at the time?

I started using and developing for BuddyPress through my work on the CUNY Academic Commons. The team behind the Commons wanted to remain true to the for-the-public-by-the-public history of CUNY itself by using free software. At the time, BuddyPress was really the only social networking tool that was free (in all senses) and that integrated well with the other tools we wanted to use. When I started building features and fixes for BuddyPress, it was only fitting that the Commons leadership would encourage me to contribute them outward, either as distributed plugins or as upstream patches.

What are you proudest of having contributed to BuddyPress?

Much of BuddyPress’s recent development has been focused on transforming BP from a somewhat quirky, largely standalone system, to a robust, modular, scalable plugin that feels — both to users and developers — like a natural extension of WordPress. I’m quite proud of the work that I’ve accomplished toward this goal over the last couple release cycles.

In BP 1.6, for example, I made some modifications to the way that directory pages are built that reduced database overhead by up to 75%. In BP 1.7, I’ve replaced our aging, labyrinthine member query methods with a BP_User_Query class that is modeled on WP_User_Query, and improves query performance by a factor of three or more. These sorts of big changes — along with countless smaller improvements — make each version of BuddyPress more pleasant for the end user, more scalable for big-time implementations, and more approachable and fun for WordPress developers.

How important has getting involved with the WordPress community been for you, and how would you convince someone up against deadlines to give something back to that community?

My involvement with the WordPress community has been transformative in more ways than I can count. Working alongside numerous other developers has dramatically improved the breadth and depth of my technical skills. I’ve created a reputation and a niche that’s allowed me to be extremely selective about which clients I work with. I’ve met a lot of great people, some of whom I’ve come to consider close friends. And I’ve been able to contribute (however modestly) to a larger policital and philosophical cause that is extremely important to me: the development of software tools that allow individuals and organizations to reclaim pieces of their online lives from commercial entities and proprietary tools.

Nearly anyone who has done this kind of work in the open and has given things away — plugins, themes, tutorials, blog posts, forum support, whatever — will have anecdote upon anecdote about how this kind of openness tends to lead to unexpected and wonderful results. That said, I can understand why some are reticent about giving things away. We all have bills to pay. And, sadly, there is no cosmic karma guaranteeing that each act of generosity be repaid in kind — every developer of freely-available WordPress tools can tell stories about hours lost, and gray hairs gained, while interacting with unreasonable and ungrateful users. So, if someone were unconvinced that community work is the smart thing to do, I’d try to impress upon them that it’s the right thing to do: if every person who’s benefited from free software gave, say, 5% of their time back into free software, the world would be a far, far better place.

What was the thinking behind Commons in a Box, and what problems did it first set out to solve that weren’t being solved effectively elsewhere?

The CUNY Academic Commons has been a model for many colleges and universities, both conceputally and technically. But reproducing and customizing something like the Commons — built on thousands of hours of development, testing, trial, and error — is no small feat. The extensibility and modularity of platforms like WordPress and BuddyPress are what make them so powerful. But these same qualities also make it daunting to set up a complex system of interacting plugins, themes, and other modifications.

The goal of Commons In A Box is to ease these difficulties. Commons In A Box does a couple of things, on your behalf, that help you get from a blank WordPress installation to a full-featured community site. First, we provide a curated list of plugins that are powerful, and we whitelist versions of those plugins that are known to work well together. We then fetch and install those plugins for you. We provide a theme that’s tailored for academic and non-profit communities, and which provides a robust set of tools for customizing layout and appearance without knowing CSS. And we handle upgrades for those plugins and themes, so that you don’t have to worry about whether, say, a new version of BuddyPress will break your site.

In short, we provide users with a head-start: instead of taking hours (or days, or weeks) to research, install, and configure WordPress plugins and themes, one can quickly get to work fostering community engagement.

What have you learned through iterating on Commons in a Box, and what might you consider doing differently if you could start again knowing everything you do now?

Technically, I think that Commons In A Box is pretty solid. Ray was the primary developer of its core functionality, and did a fantastic job building something that can easily be maintained and extended. And our theme developers, PressCrew, built a theme that strikes the perfect balance between ease-of-use and flexibility, without making any sacrifices on elegant design.

My biggest challenges during the development of a relatively large project like Commons In A Box were related to management. Most of the time I devoted to the project was not spent writing code, but doing code reviews, managing deadlines, leading testing, handling communication, and so on. I discovered that, while I like (and think I’m good at) playing a leadership role in a public volunteer project like BuddyPress, leading a grant-driven project like Commons In A Box takes a whole different skillset. I don’t really have the chops, or the desire, to do project management for my day job.

With Commons in a Box, Anthologize, Participad, and in a lot more of your work besides, there is (or seems to be) a real emphasis on community publishing. Which comes first for you — community or publishing — or are the two inextricably bound together?

The core idea that motivates my work with free software is that users should have control over what they do and produce online. It just so happens that I came to software development through BuddyPress and WordPress, so that my professional emphasis has been on tools for web publishing and community. In another universe, I’d be working on a different kind of free software

That said, community and publishing software are particularly important insofar as they both enable kinds of activity that are central to the way we conceive ourselves: the things we write, and the connections we make with others. Those who develop these kinds of software, then, have a special privilege and resposibility to respect user freedoms.

What roles do you see WordPress and BuddyPress playing in the ongoing transformation of education, and does it make a big difference that they’re Open Source?

Education (especially the liberal arts college experience) is often described as the process of turning youth into citizens. When a student takes a course in philosophy or physics or history, she’s gaining a set of tools for participation in society, for representing herself and her needs in a respectful relationship with the world around her. The rise of free software parallels this conception of education in a nice way: things like WordPress and BuddyPress are tools that enable students to become fully realized agents, individuals with control over who they are and what they create.

From a philosophical point of view, it’s far more important that these tools are free (as in speech) rather than that they’re open source. Most students are not technically inclined, and the idea that their favorite piece of software was developed using a given methodology is probably not very interesting to them. What does matter is that free licenses like the GPL protect their rights to use the software as they see fit.

More concretely, the ideas behind free software are very much in keeping with the public-engagement goals of universities, especially public ones. That means that schools are, more and more, embracing free over proprietary software. This has a cascading effect: students are creating content using software they’ll continue to use after leaving the university; the university is free to modify the software however they’d like for their own purposes; development funds go toward hiring free software developers who are generally local to the university and sympathetic to its purpose, rather than toward huge licensing fees paid to faceless software companies. It’s an amazing trend, and I’m proud to be playing a role in it.

Do you see a point at which educational and other organizations will be able to ditch proprietary networking, teaching and knowledge sharing solutions for Open Source alternatives? What, if anything, stands in the way of that happening?

I think it’s already happening, little by little. About five years ago, the CIO of one of the CUNY campuses told me they couldn’t support WordPress because “they didn’t have a Linux person on staff, and they never would”. In the fall of 2012, I helped this same campus move its externally hosted, guerilla WordPress installation to a Linux server supported internally by the IT department.

Leadership in campus IT is extremely conservative. For university CIOs, “free and open source software” has traditionally meant software that’s insecure, feature-weak, unreliably, and — most importantly for them — unsupported. In the last few years, the zeitgeist has shifted, at the same time that free software itself has gotten better. The marketplace that provides services and support related to free software, from big companies like Red Hat and Automattic to individual consultants like me, has played a big role in making free software seem less like a gamble to
these very risk-averse individuals. People on the academic side of the university — faculty, deans, provosts — generally don’t need much convincing to be sold on the practical and moral benefits of tools like WordPress, so as CIOs gradually find the idea of free software more palatable, there’s a potential for the floodgates to really open on its use in universities.

Has working at CUNY afforded you development opportunities that you might not have been able to give time to if you working in, say, corporate or startup space?

Definitely. CUNY has historically been a very particular kind of social justice institution, catering to a huge underserved subsection of New York City. So it’s been a fantastic place for what I’d call “activist software development”: the building of tools that are conceived to suit our specific needs, but are also designed from the start to be given away.

As I’ve done more and more work outside of CUNY as a freelancer, I’ve found that this same spirit — the desire to serve through building — exists within educational institutions all over the world (though sometimes not as openly as at CUNY). I’m really pleased that I’ve been able to do contract work for a wide variety of schools, playing my part in spreading the good news of free software.

On a personal level, I don’t think I’d deal well with corporate or startup culture. I get bored easily, and thrive on learning new things and dealing with new people. My preferred lifestyle is to spend 30 or 40 hours a week doing interesting and highly varied work, and to spend the rest of the time with my family. Pumping out 60-80 hours weeks working on a single app as part of a startup? That’s a young man’s game

What are you most excited about working on next, and what would you like to see happen longer term for WordPress and BuddyPress in your context?

By design, more and more of my work has been about tool-building, rather than website-building. This kind of setup has worked really well for me, satisfying my dual desires to keep my work varied and to have maximum impact. I’m currently in the process of working with a couple of different colleges on new tools to make WordPress and BuddyPress work better in the academic context: from beautiful BuddyPress portfolios, to full-featured BP file management, to group RSS curation in WP. Beyond the next six months or so, I don’t know what I’ll be doing — but that too is part of what’s exciting!

One of the long-term goals I have for BuddyPress is for it to play a meaningful role in rethinking a truly distributed social web. Today, so much of our social content is locked up in centralized silos like Facebook and Twitter. BuddyPress eases this centralization at a small scale, by enabling niche communities, like schools, to set up their own internal networks. But I can imagine taking this idea even further. BuddyPress (much like WordPress already is) could be a tool for individuals to take control of the social content they produce around the web. BP could aggregate content you leave elsewhere — a comment on someone else’s blog, say — while federating with the BP installations of your friends and colleagues. The open standards that will make this kind of personalized, decentralized social hub possible are starting to mature, and I’m anxious for BP to play a role in putting this kind of control within the reach of the masses.

Quick Overview

If you’re interested in web design and development and want to expand your horizons across a range of sizzling hot topics, you’re probably going to want to plug your ears into the Boagworld Show. Paul Boag and Marcus Lillington of Headscape, alongside frequent guests, take on big subjects like analytics, best practices, and building sites for ROI, and all in their quintessentially British fashion.

Image based on Blue Marble 2002 by NASA Goddard Photo & Video, CC-BY-2.0.

Quick Overview
Hosted by Ryan Imel and Brian Krogsgard, the WP Candy podcast covers plugins, plugin reviews, WordCamps, themes, community news, and more in their show. Give those reading eyes a break and tune in to the WP Candy podcast to keep up to date on WordPress happenings.

Image based on Candies by Moyan Brenn, CC-BY-2.0.

You have a background in industrial engineering. How did you get into working with WordPress, and have you found that your industrial engineering background has influenced your work with WordPress?

I’ve always been intrigued by the web, but I didn’t give any real consideration to building websites until I was in college at Auburn and thought I had a few good website ideas. They weren’t good ideas, but fortunately I managed to find WordPress in the process of figuring that out. I continued to be fascinated by how easy it was to create a basic website with WordPress, and for a while would periodically tinker with a new idea, but between 2008 and 2010 I was much more focused on my new engineering career.

I started blogging around mid-2010. I was hacking around with my personal website and of course coming up with new ideas. But this time around I realized that I enjoyed making websites more than I believed in any of my ideas for websites. I also realized just how much I liked to write. I got hooked on WordPress and web development in general and never looked back. I spent countless hours reading, tinkering, and blogging so I could learn more and more about WordPress.

Early on, I don’t know that my Industrial Engineering degree did too much to benefit my web endeavors. But now that I am a full-time programmer and consultant, I consistently see the benefits of my Industrial Engineer’s mindset and focus on core business goals in tasks that I perform. Plus, Apple CEO Tim Cook is an IE grad from Auburn, so I feel like that gives me some major street cred, right?

At what point did you realize that you could make a living with WordPress, rather than tinkering with it as a hobby?

By spring 2011, I knew that what I was doing wasn’t going to fulfill my career ambitions. I had found my professional passion, and I started thinking about how I could possibly work on the web full time. I knew little to nothing about professional web development or the WordPress economy, and I certainly didn’t know just how in-demand WordPress developers were.

I thought I was going to have to take an enormous leap of faith and leave a well-paying job with great benefits and become a freelancer. So I just kept building websites for family, friends, and fun to help prepare myself. And then in August 2011, I saw a tweet from one of the largest and oldest web development agencies in the state promoting a full-time position for a WordPress developer. I was shocked, and felt like I must at least send them an email, even though I still didn’t think I was quite “ready.” A week later, I had a job offer in hand from Infomedia to be their lead WordPress developer.

You recently launched Post Status. How do you pitch that to the unawares, and what inspired you to put it together?

I typically define Post Status as a “WordPress News & Links” blog, but really it’s just a short-form blog where I link to things I like while adding a bit of context to the conversation. Also, other people periodically submit posts that they find interesting. I’ve enabled up-voting on the site as a method for visitors to offer additional insight to other readers on whether the linked post is interesting or not.

I put it together simply because I wasn’t satisfied with existing methods for consuming WordPress-related information. I’ve always enjoyed Hacker News for broader tech news aggregation, but it’s still a bit impersonal and obviously not WordPress-centric. I also love the style of the Next Draft newsletter, as it’s a collection of the top ten news items every day, curated by Dave Pell. Dave’s own “voice” really shines in his newsletter, while simultaneously driving me toward the articles he links. My goal is for Post Status to be like a hybrid of the two.

Tell us a bit about the thinking behind how Post Status works, and how you set it up to be as democratic and user-focused as WordPress from the get-go.

I’ve seen a number of WordPress news sites come and go, for a variety of reasons. But most WordPress news comes by way of a blog post anyway, so re-writing longer-form blog posts as “news” is a bit silly in my opinion. So Post Status merely attempts to drive traffic to the source, and add context in as few words as possible to help readers discern whether they want to read the original article.

I rely heavily on user feedback, submissions, and validation (by voting) in order to make Post Status its best. In a perfect world, Post Status would be a go-to resource for anyone interested in WordPress. I want it to be part of people’s daily routine. And I can’t do that alone. If Post Status helps someone’s blog get more attention when they’ve written great content, and also offers a source of quality information to readers that they otherwise may not have found, then we all win.

By day you’re the lead WordPress developer at Infomedia. Can you think of a project you’re particularly proud of having worked on recently? What made it stand out for you?

One of my favorite sites we’ve done at Infomedia is Weld for Birmingham. Weld is a weekly paper in town that has done a great job of balancing print and online media. They have a small staff, but they also encourage community members to start their own blogs on Weld. I love how passionate they are about Birmingham and how focused they are on high quality local journalism.

From a technical perspective, we built a responsive parent theme using the Hybrid Core drop-in framework and a child theme for the blogs in their Multisite network. We’re using a custom post type and Posts 2 Posts so they can relate their online articles to their print issues. During the process of building this site, I discovered just how much advertising technology isn’t keeping up with responsive design.

My talented coworker, David Hickox, is responsible for the beautiful design. Weld is engaged with their online community and they love WordPress. They are a joy to partner with, and the project has been very rewarding personally.

How important has the WordPress community been in getting and keeping you involved with WordPress, and would you encourage others to get involved on some level?

My relationships with other members of the WordPress community are incredibly important to me. I wasn’t hired at Infomedia because I was a proven developer. They took a chance on me, because they were just getting into WordPress, and saw my commitment to staying engaged with the community. I learn every day from many people in the community, and cannot stress enough just how valuable my relationships are. WordPress has a very special community atmosphere, where even the most talented WordPress professionals in the world are approachable and helpful.

My wife jokes with me about my “internet friends,” and I always love when I get to turn an “internet friend” into an “in real life” friend at WordCamps and meetups.

You’ve written about pricing products and services on your blog before. What’s the most important thing that someone just getting started with their WordPress business should keep in mind about pricing, and what do you wish you’d known years ago that you know now?

Clients hire consultants for tasks they can’t handle themselves. Therefore, creative and technical aptitude is assumed from the get-go. Being a great programmer isn’t going to make a client an advocate. Excellent communication skills, complete honesty, and doing what you say you’ll do will make a client an advocate every time. We should price our work based on the value we provide to the client, but we also need to make sure the client will look back on the project as a positive experience as a whole. They will never see the value in our code if we don’t communicate properly and make good on our promises.

As far as more practical pricing tips from some people I really respect, the Code Poet ebook on pricing is exceptionally good. I promise I’m not just saying that because of this interview. Mark, Remkus, and Shane are all top notch members of the community, and it’s very nice of them to share their knowledge and experience.

I certainly wish I knew a few years ago just how in-demand WordPress developers were. When I first thought about making the jump, I didn’t know how many agencies were seeing the popularity of the platform and desperately trying to find talent. I could’ve started working full time with WordPress sooner than I did. You’ll never think you are “ready” as long as you are learning, because you’ll always see things you still don’t know. I tell aspiring developers to just go for it. Start sending emails to local (or remote) companies and give them an honest overview of your skill set. Someone will love to hire you, and then you can learn on the job.

How important would you say it is to provide documentation or training to clients, and what’s in it for the designer-developer itching to move onto the next project?

Unfortunately, building something doesn’t mean the user will automatically know how to use it. Documentation and/or training is pivotal. I talk a bit more about how to offer users help on WP Realm, but in addition to those methods, nothing beats real in-person training. I usually leave training sessions with more personal notes on things I can improve in the UI interface of a particular feature, just from watching them use it for the first time, than items the client requests.

As for what’s in it for the developer, nothing is worse than building a feature that goes unused. And if they don’t know how to use it, why would they?

Tell us about the Happy Theme you designed and shared with the community, and what you learned from the process of putting it together?

The Happy theme started as a project to design and develop a theme I’d release to the public. However, I simultaneously needed a new base theme for our Infomedia client sites. So, Happy hasn’t really become the finished theme I wanted it to be yet, because I focused on creating a base theme first.

On our client sites, we use a forked version of Happy that we’ve consistently iterated. We were in need of a flexible theme that we weren’t afraid to fork when the work necessitated it. Because it’s built on Hybrid Core, that’s easy. The framework lives in the “library” folder, but doesn’t assume anything about the theme markup or specific features. Therefore, we can build most sites as a child theme, but if we need to fork the parent, it’s no problem.

Before long, I’ll finish up the Happy theme the way I initially imagined it, with all the goodness and flexibility of our Infomedia base theme. Then I’ll finally submit it to the repository. In the meantime, patches are welcome!

The biggest thing I’ve learned in theme development so far is that thinking through a theme architecture only goes so far. Nothing beats putting it to the test in the real world to see how both users and other developers will use it. My teammates at Infomedia make for a great test group!

Which three things would you underline as essential to anyone wanting to carve their own place in the competitive WordPress design and development world?

1. Never stop learning. New trends and techniques are always emerging. I often finish a project and immediately want to go back and change something based on a new technique I learned. Read blogs, books, and follow industry folks on Twitter to stay up to date.

2. Blog. We build things for other people every day using WordPress. We need to eat our own dogfood and use WordPress ourselves. I’ve learned so much by blogging consistently, both about how to use WordPress efficiently and just by writing about topics I want to learn about. Also, blogging has helped me get my name out in the community more than anything else I’ve done.

3. Be nice. There are enough inconsiderate people in the world. Follow the golden rule. Treat others how you would want to be treated, whether they are a client, a colleague, or a random person you encounter on the internet. This isn’t always easy, and I often fail, but if we all made a conscious effort to be nice to one another in our daily interactions, the world would be a better place.

Quick Overview
When you’re making things with code, it can be hard to keep up with the learning — the reading and research you need to do to make sure that your work reflects the latest ideas, techniques, and security best practices. Thankfully, if you build themes, The WordPress.com Theme Guide does the heavy lifting for you on escaping, internationalization, queries, scripts, styles, plugin conflicts, and more in an easy-to-scan checklist format. You’re welcome.

Image based on “Remington_Noiseless_Bedienungsanweisung_ 2” by Georg Sommeregger, CC-BY-2.0.