If you’ve been a designer for any length of time, you’ve probably had clients request things from you that go beyond design and into the realm of development.
Web design, as you know, involves the visual and structural design of a website. You’re making creative decisions about things like layouts, navigation, and user experience. There’s certainly a good bit of science behind the decisions you make, but it’s more art than science.
It’s like architecture – you come up with the plans for a site, but developers are the ones who actually put the ricks (aka tech) in place for the site to exist. You aren’t the one out digging a foundation and hanging drywall; you’re just saying where the foundation and drywall should go.
Then there’s web development. Developers are the folks who actually go and build a website. If we’re talking art vs. science, development is definitely heavy on the science end.
Developers take a concept and find a way to execute it, but generally speaking aren’t the folks who are pouring hours of creative energy and thought into the concept. They deal in coding and tech and construction – they’re like the builders, not the architects.
There’s a caveat and you’ve probably already thought about it: designers totally build websites! But they do so using themes, plugins, and usually some CSS or HTML5. They’re building the site from the design “blueprints” (to continue the architecture idea), but they’re essentially customizing frameworks and elements that were created (coded) by developers for the specific purpose of being assembled by designers.
Very few designers will actually design a site and then code it from scratch.
And those designers who do aren’t really designers at all. They’re hybrids.
So what is a hybrid web designer/developer?
Designers design; developers build. A hybrid web designer/developer designs and then builds.
If you love coding and building beautiful, effective websites from the ground up, you might be a hybrid.
If you make some stuff happen in CSS and maybe you’ll build a page with HTML now and then, you’re probably not a hybrid. You’re still awesome – a designer who’s able to code in CSS, HTML, and more. The more coding skills you have, the more robust you are as a designer…but that doesn’t necessarily mean you’re also a developer.
It works the other way, too. If you’re a serious coder and you know how to put together some basic websites that are easy enough to use but don’t really focus on user experience, conversion goals, or positioning, you might not really be a “web designer” in the primary sense of web design.
You, too, are still awesome! But not all developers should be designers, and there’s nothing wrong with focusing just on coding and leaving the worries about multiple menu placements and calls to action to someone else.
But, of course, if that stuff fascinates you and you’ve looked into it – or you’ve even taken coursework to learn more about the purpose of a website and how to make designs more effective, you might be a hybrid!
Benefits of going hybrid
These days, hybrid web designer/developers get a lot of buzz, and with good reason. The more well-rounded you are, the more robust of a service provider you can be.
Designers who truly understand the development process can offer expert advice on what’s doable and what’s not, which can open the doors for a lot of creativity and – perhaps more importantly – shut the doors on a lot of stuff that seems cool on paper (or in wireframes) but really isn’t feasible from a construction standpoint.
As a hybrid, you’re what some people call a “unicorn” – a magical creature we hope to find someday, but who we don’t actually think will be able to.
Just think – a client comes to you and says “I want this! and this! and this!” and you have to bring them down to Earth because, as awesome as Divi or Genesis is, there’s no way to make all those ideas happen within those frameworks – and that’s what you’re limited to.
Now imagine being able to blow the roof off the framework, giving your client anything and everything they want despite any particular theme’s limitations, and then charging a premium price to do it.
Sounds awesome, right?
That’s because it really can be.
Plus, there’s an employment disparity between web designers and developers, with developers having many more available jobs and pulling in much more money for doing those jobs. Tapping into the developer market is a great way to make more money, if coding is something that interests you.
Drawbacks of doing both design and development
When you advertise yourself as a hybrid – or you take a job as someone who can design and code – what you’re doing is positioning yourself as one person, doing the work of two people.
You may be a powerhouse, but you might also be cutting yourself off at the knees.
With two focuses, you could probably become “pretty good” at designing and at coding, or maybe really good at one end and decent enough at the other end. But it’s pretty challenging to become super-awesome at both. You’ll have a hard time really becoming a leader in either field.
In other words, you’re so well-rounded that you can’t really specialize in both.
That’s great for some folks. A lot of websites, after all, don’t need a hugely complex, robust design. Plenty of designers get their bread and butter from run-of-the-mill bloggers and small businesses who just need a basic site. And if that’s your sweet spot, you’re in a prime position to do really well.
Final thoughts on being a hybrid web designer/developer
If you really want to be the best, to be the absolute best at what you do, you might find that focusing on design and development together is too much for one brain. No shame in that – we all have our sweet spots.
But the pull of being able to execute on both design and development will give you incredible insight, and it might be worth the fight to make it happen.
To overcome the challenges of being a hybrid, you must always, always, always be learning and practicing. You might not be able to lead the pack in either of your fields, but you can certainly keep up as long as you focus.