Live data from Hacker News

Thoughts on Paul Rand

acg.media.mit.edu

41–42 of 42 posts

Re: Thoughts on Paul Rand

#41
post #20

Earlier quoted context omitted.

There can be problems with this approach, specifically, "The best way I know how" may not be the best way for the client. There are pros and cons with nearly every potential solution and it can be beneficial to discuss the pros and cons of more than one solution with the client before proceeding. It's arrogant to assume the best way you know how is the best way for the client. For example, if you only know Ruby and t…

As your comment shows, "the best way you know how" when applied to yourself includes the realization that a PHP solution might be better for a PHP shop. Throw in another bunch of such realizations and a life long effort to actually come up with such realizations and you will understand why Paul Rand's approach is acceptable. He set out to solve Apple's problem. Not his initial and naive conception of their problem. H…

NeXT's problem, actually. Rob Janoff created the Apple logo.

Re: Thoughts on Paul Rand

#42
Is it just me or is everything he says very abstract? Sure he's good at his craft, but all the things about everything being subjective, and design having many meanings, and that anything can be artistic... it just seems like he has very generic sort of explanations for everything.

I guess to be a good designer you have to have this attitude, but in today's business, the sort of attitude where you're like "I'll show you a single logo, and you won't have other options" won't cut it.

Design is subjective and it will always be, so not giving your client many options is just plain stupid and will make you poor before you know it.

Post reply on HN