If you make your living from developing WordPress sites, odds are good you have at least a cursory familiarity with PHP and most likely quite a bit more.
Maybe you can customize themes – or even build one from scratch – and act as a proper admin for your clients. Even so, you’re likely to run into an occasion where your skill set doesn’t match what the client wants. And that can be a real bummer. You’re either forced to outsource part of your project or turn it down altogether. Neither scenario is ideal.
If you run into this issue more and more often, it might be time to consider adding back-end development to your list of offerings. There are a few things you should consider before jumping into back-end development, however.
Developing Outside of WordPress
Back-end development means you’ll be venturing outside of the WordPress development territory you’re most familiar with. This can be scary, as venturing into anything new is scary. What I’m trying to say is that not everything is going to look like functions.php. And that’s perfectly okay so long as you know that going into it.
One of the biggest things you’ll encounter is called Object Oriented Programming (or OOP for short). WordPress doesn’t use it but you might wish to add it to your service list because of its flexibility. Plus, it’s utilized by a lot of other frameworks out there (more on that later).
So, for the uninitiated, OOP uses classes to group together functions. These functions may be referenced later to be put into action. Instead of writing out a series of functions as you do in PHP (an immediate cause and effect approach) with OOP you have to sit back and think about how your code will be structured before you write a single line. That might sound daunting, but if you have a penchant for organization, you might really excel here.
A really great example of this kind of development is offered up by Jay Hoffman of Torque. It’s the WordPress Plugin Boilerplate by Tom McFarlin, which offers a wide-angle view of how OOP can be used. It’s all about creating structure first then creating whatever it is you want to make.
When you build with WordPress, it’s easy to take a lot of things for granted. It comes equipped to do a lot of things without you having to lift a finger. Which I’m definitely not going to complain about. If you venture outside of WordPress, however, you’ll quickly notice that other frameworks don’t have everything built-in, which means you’ll need to build them yourself. What you create will be less bloated than WordPress but it will take a lot more work. That’s just a realistic fair warning and not meant to discourage you from giving it a try. I’m just a big believer in approaching things with eyes wide open.
Front-End Development Carry-Overs
As a front-end developer, you likely have plenty of experience working with PHP and just generally digging around in the code in WordPress theme files. And while that will certainly help you make the leap into back-end development, it’s not the be all and end all of preparation, I’m sad to say.
And since we’re talking about server side stuff here, I’d be remiss if I didn’t mention the fact that all the time you’ve spent fixing WordPress sites will come in handy. If you’ve ever dealt with a broken site – who hasn’t? – you know the order of operations to take to fix it. This step-by-step process is something that applies directly to back-end development and that you’ll likely use on a regular basis.
Learn Something New
While there’s absolutely no reason why you have to get into back-end development, it can be a smart move for many WordPress developers. Why? It comes down to one key term: diversification.
The more areas of development you’re familiar with, the more jobs you’ll get. You can think of it as added tools in your toolbox. All of these skills you amass translate directly into dollars and cents in terms of what you can create for your clients. And the fewer times you need to outsource aspects of a project or even turn down projects, the better off you’ll be.
Of course, there is something to be said for being a specialist. That certainly has it’s advantages, too, especially if you come to be known as the very best in the game. But since that title is reserved for a limited few, it might be a better option to diversify your portfolio and offer a wider variety of services so you can serve a wider range of customers.
If you like to live dangerously, dive into Ruby on Rails. And that’s just scratching the surface. There are way too many frameworks out there for me to name here. Just know that there’s no law saying you need to be proficient at everything. But if you want to become more proficient with back-end development, your options are wide open. And each has ample support documentation and community involvement to help you out every step of the way. And the more you learn, the more you’ll discover how all of these frameworks can work together with one goal in mind: to create better websites.
It’s normal to be hesitant at the prospect of pursuing back-end development when you’ve been working as a front-end WordPress developer for some time. But just because something may be perceived to be a challenge doesn’t mean you should avoid it. In fact, learning new skills can bolster your service offerings and make you a more in-demand, vital developer to a wider range of clients.
And at the very least, you should see your front-end development skills improve. The better you understand how things work on the back-end, the more adept you’ll be at writing clean code and anticipating potential problems. Basically what I’m saying is this: Even if you decide not to offer this service to clients, it still won’t hurt to learn it.
Do you offer back-end development along with front-end work? Thinking about expanding your skill set? Or are you content with where you’re at. I’d love to hear your thoughts!