Avid web designer and developer striving to make the web awesome. Obsessed with UI and graphic design. Joshua is a DZone MVB and is not an employee of DZone and has posted 7 posts at DZone. You can read more from them at their website. View Full User Profile

Designers vs. Engineers

09.26.2012
| 9723 views |
  • submit to reddit

This is something I’ve been meaning to write about for a long time, but I never quite got around to doing so until now. It’s a frustrating topic that involves a lot of tension between people who are a part of two seemingly different worlds — designers and engineers.

It was this statement on Hacker News that finally drove me to write this essay:

If you want to design table lamps and dribbly teapots, keep churning out this hogwash. If you want to change the world, start designing with your brain, not your felt tip pens. The world is full of vital, urgent, life-or-death design problems, but they need substance, not style.

While I don’t entirely disagree with the gist of this statement, it’s intentions (in and out of context) provide a real disservice to everyone, especially designers and engineers.

First, let me give you a little background: my life choices have put me in a particularly interesting position of having thoroughly experienced both worlds. By day, I am a design student and by night, a web developer. I build, design, code, conceptualize, implement, and envision. I have an understanding of the frustrations of poor kerning, bad typographic choices, and frustratingly unclear design decisions. I also understand poor coding standards, the necessity (and avoidance) of writing good tests, and the value of optimization.

With that said, there is a frustrating dichotomy between designers and engineers. Why a dichotomy? Simple — designers and engineers are cut from the same cloth: we’re all solving complex problems, using our background knowledge to derive a valuable and functional solution.

The Engineer’s Perspective

Designers don't take criticism very well and seem to be allergic to data. Might as well be arguing about feelings or unicorns.

I’ve had discussions, at length, with engineers who seem to feel that design is “unnecessary” or a “waste of time.” A time-worn and tired example oft given by engineers is that of Google: “Well, Google didn’t use designers to build their website!”

Google, circa 1998

Yes. That’s true. We get it, Google hit the nail on the head, relative to other web design at the time. However, it is an exception, not the rule. And guess what? In 1999, they hired Ruth Kedar to refine and redesign the logo. Additionally, the home page has seen countless revisions and changes over the past 13 years, with the help of (data-driven) designers.

To an engineer, design seems like an unnecessary and tangental part of the creation process. “It just needs to work,” we say, “it doesn’t need to be pretty!” That simple little statement ignores designers’ years of experience dealing with how humans perceive and interact with the things they use on a daily basis. Colors, shapes, forms, grids, typography — these are all aspects of design chosen with a careful eye and an understanding of how they will affect the overall perception of an object, thing, or experience. Not simply a haphazard attempt at creating something “pretty” or “nice looking.”

That is not to say that there isn’t plenty of bad design that puts form over function. What I’m saying is that you should ignore the bad design and make an effort to understand good design.

The Designer’s Perspective

Designers, on the other hand, see engineering in a completely different light. Given a task, we set out to create something with, often, little regard for the implementation aspect of a design. It is not with cruelty and inconsideration that we do this, however, but with the best of intentions: we apply our skills as we know them best, putting to use our understanding of how people perceive “things.”

However, we should truly work to have an understanding of the engineering difficulties we are creating through our designs. That is not to say we should not push the envelope, bend the rules, and break tradition — but to do so with the knowledge of the difficulty involved in implementation.

 Schwinn bicycle

To ignore the history and the reasoning behind a particular aspect of engineering — writing it off as merely ugly or “bad design” — is to be a bad designer. While it that may be true a portion of the time, it would be irresponsible to overlook.

Happiness in Consideration

In the web development world, I often hear developers insisting that web designers must learn development to be able to design properly. I also frequently hear designers venting their frustration about an engineer who does not see the need for a certain level of precise detail in a design.

I’m not advocating that designers should learn all the ins-and-outs of development, or how to cast metal forms, or how to vacuum form plastics. I’m also not advocating that engineers should learn all the intricacies of typography, color theory, or the grid.

However, if you’re working with a designer or engineer, it would be nice to at least have a basic — even just surface — understanding of what is involved in their work. Ask questions, do some research, try to find out more. Everyone will get along a little better.

Published at DZone with permission of Joshua Gross, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)

Comments

Chris Travers replied on Thu, 2012/09/27 - 4:26am

I think a big part of the problem is that a lot of hackers confuse "design" with "marketing."  Good design is an intersection of art and engineering.  How will this be used?  How can we make it pleasant to use?  Those are, IMO (as an engineer) the questions of design.

 But all too often we see empty design.  This is what happens when the real design engineers (gotta use that label in the context of your article) and the product engineers are directed by the marketers.

 I think it is important to avoid lumping "design" in with "marketing."  "Design" is about how to make something appealing and pleasant to use.  "Marketing" is about communicating a message. They two may intersect, but good designers are more like engineers than they are like marketers. 

Jon Williams replied on Fri, 2012/09/28 - 4:22pm

Ok all you "Engineers", here's a challenge for you.

Take out your degree, Does it state the word "Engineer" anywhere on it?

95% of you can't find that word right?

 

So we have a distinct pecking order established in this Biz.

On top are the Engineers (With real Engineering Degrees),

Then we have Computer Science people, who can be somewhat skilled designers/developers. But are fraudulant if refering to themselves as Engineers. Remember if that degree doesn't say "Engineer", well you know it ain't true.

And at the bottom there are people who've managed to figure out how to do proper HTML5, CSS3 and can do respectible photoshopping. These are the designers. They can be amusing, and failing that they can always fall back to being decent targets to throw things at.

 Any questions? 

 

ps. dzone, you need to hire an Engineer to help you get a spell checker into this editor.

Chris Travers replied on Sat, 2012/09/29 - 3:16am in response to: Jon Williams

Question:  Is Gustave Eiffel best remembered for his engineering or his design?   Was he seen as great in his day for which?

 Any civil engineer could have designed the bridges over the spans that Eiffel did, but it took Eiffel to do it with grace and skill, blending together the aesthetics of Romanticism and Modernism in a way which had that sense of grace which characterized his work.  That he was an engineering genius is certainly not to be doubted (nobody else could have designed his pioneering tower in his day), but his greatness in his day was at least as much of a fact of being a great designer, i.e. designing bridges and railway stations that were pleasing to look at, as it was of being an engineer.

 Who here remembers his work on the structural elements of the Statue of Liberty?  No, we remember him for his bridges and buildings, and of course the tower which bears his name. 

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.