Hacker News Reader

Comment by usaar333 | Hacker News Reader

Unfortunately, you've really jumped the gun here.

I'm a programmer who isn't so hot with design. But I certainly know how to use a program to layout objects; that's trivial to learn on the grand scheme of things.

What I (and other non-designing devs) don't get is how to know what "doesn't work". I have at most a fuzzy idea of what are considered good and bad designs, much less how to produce them.

One of the biggest issues is the lack of feedback. With beginning programming, you are getting constant feedback from the computer. It even tells you where you are going wrong (line numbers, variables, etc.)

Design lacks such an objective feedback system. Sure, there's the times when your friends will agree that iteration B is superior to A. But actually getting feedback on what to do next? Pretty tough.

View on HN

Time to learn the term "design brief," which relates to the design like a program specification relates to the program.

What is the design supposed to accomplish? What should it convey? What kind of reaction should it elicit from the viewer? While these ideas may not be completely objective, they can be expressed in written form. Doing so is one way to bring some objectivity into the the process, as well as a way of keeping everyone "on the same page." Adhering to the spec is a also a good way of finding out if your spec is useful or not. If you find the design veering away from the brief, go back to the beginning and start again; re-write your brief, and re-iterate the design.

Now a quibble about your mention of knowing how to use a program to lay out objects. (Note, "lay out" is the verb and "layout" is the noun.) One such "object" is of course type, and learning how to size, lead, track and kern your type is more than just placing objects (letters) in proximity. Knowing how to use the program is one thing; achieving great visual results is another.

How to learn what works and what doesn't? Get some design annuals, subscribe to design magazines, start reading design blogs. Most importantly, find a good designer who will critique your work. All of these activities will develop your eye and your design sense.

In my opinion there is nothing more frustrating than starting working in a layout program. I usually just end up feeling like I am moving crap around on the screen until something sticks.

The best way to start is to hear how a well spoken designer will explain their client's problem, how they worked through it, and pick it apart. This will help you understand the dynamic conversation between elements that occurs in design. I would recommend reading a few books from older, well regarded designers who's work has stood the test of time. Paul Rand, Herbert Bayer, and designers from the Swiss design movement stand out as good examples of clear, well reasoned design that is easy to understand.

While doing this, I would recommend that you try taking some of their designs, and recreating them. Try making a version that looks web 2.0 like, one in black in white, etc.

Reply on news.ycombinator.com