Designers Deserve Better Developers

If you’re a designer who has even thought about outsourcing development, you’ve heard the horror stories of bad dev behavior.

I call them code bros.

The code bro sends 2-word responses at 3 am - if you’re lucky.

It’s the code bro sending surprise invoices to your inbox seemingly at random (how can you even budget for that?)

And, I swear to god with the code bro ghosting juuuuust before handoff.

This kind of code bro behavior is a bummer, and hopefully a thing of the past.

Designers deserve a better kind of development experience.

So, let’s focus NOT on the code bro of the past - but the development partnership of your future (that’s a music cue if I’ve ever seen one).

We need to talk about how the right dev elevates your design game (and client experience).

The right dev is someone you want to work with.

Honestly, you can stop reading now, because this one is just so important.

ahem…

Since we’re talking about a collaborative sport here, you must vibe with your developer (at least a little).

This is the intangible stuff that you can’t really put your finger on, but you know it when you see it.

Say you’re deciding between two developers:

• Dev 1 has tons of experience and a website that makes you physically jealous. But the convo crashes hard after the small talk intros.

• Dev 2 is a solid new dev. You like their portfolio, but you ran over on your meeting bc you both couldn’t shut up about the latest Miranda July novel.

I’d go with #2 every single time.

It is in the conversations between designer and dev that the website itself is created. So much good, juicy, kinetic stuff happens in the back and forth.

You’ll get way more out of someone you’re a good match, than you will if you make the call on experience or resume alone.

Who wants a dev who just doesn’t quite get your jokes? Not me, I can tell ya that much.

I am not saying DON’T go for the better dev.

But, the more you want to work with your dev, the more you will work together. And, the more you work with a developer, the more you’ll get to know each other, and the better your project relationship becomes.

That’s just math.

Design Systems are love

A design system is a tangible set of components and guidelines that define the design itself.

Call it a style guide.

Call it Peter.

Whatever you call it, having a set place where the visual language of your design is located will do wonders for any designer/dev relationship.

Pssst, it’s not really about the design system itself - it’s about creating a common language and clear communication channels that you and your dev both use.

This design system, aka style guide, will contain things like colors (hex codes), typefaces, typography hierarchy, button styling, and any other visual components taking place in the design.

The dev’s job is all about proportion and translating your static mockup into a responsive site. So, it’s key that there’s consistency in the design system itself.

If you work with multiple platforms, you’ll be grateful for a developer who points out certain limitations or inefficiencies in your design system at the beginning of a project.

For example, in Squarespace, there are only Headings 1 thru 4 available in the built-in style settings. Having additional heading styles would involve CSS styling.

Whereas in Webflow and other platforms, more than 4 heading styles are programmable. So, custom CSS would not be involved.

It’s little details like this that will save you (and your dev) a lot of time and heartache in your projects.

A design system can reduce a project timeline by hours and days (there’s variables here, but you get my point).

Put the bells and whistles down, my dear.

Yes, you deserve the fanciest, shiniest, swoopiest website that’s ever existed. It should change the concept of the website as we know it, right?

Well…

I say this with love, but less is always more.

Good dev is NOT about being all in your face with animations and mind-altering JavaScript.

Good dev is consistent dev, good dev is user-friendly, and good dev is built to last.

You want a dev who understands coding languages and yadda yadda yadda.

But, REALLY, you want a developer who will help you understand the downsides of adding 17 custom sections with plug-ins and JavaScript and all the stuff vs sticking to one consistent animation throughout the site.

A good dev partner is not a yes man. You want a dev who will stand in your way when you need them to.

Having the right developer is about having the right developer for you.

Set your collaboration up for success by establishing design systems and communication channels to make your project effortless and organized.

Then, allow the magic to happen in the vibrant conversations that are bound to happen when creating between designer and developer.

Here’s what Charlene Timbol of Mindful Charlene says of outsourcing dev:

“This experience reinforced the importance of outsourcing development, not only for my own benefit but also for the satisfaction of our clients.”

If you’re ready to collaborate with the dev partner you deserve, start a project with us here.