Live data from Hacker News

Thoughts on Paul Rand

acg.media.mit.edu

31–40 of 42 posts

Re: Thoughts on Paul Rand

#31
post #22
post #10

Earlier quoted context omitted.

Exactly what is the point of this comment?

The point is to find out which products John Maeda has worked on?

Some of it is here: http://www.maedastudio.com/

People sometimes look at his work and think it's very simplistic and/or retro. Part of the art is the process it took to get there.

Re: Thoughts on Paul Rand

#32
post #20
post #18

One great story about Paul Rand: "He is one of the most professional people I've ever worked with, in the sense that he thought through all of the formal relationship between a client and a professional such as himself -- obviously very deep thoughts about this -- and therefore he had very clear conclusions about what the relationship meant to both parties and how it should be conducted. For example: I asked him if h…

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…

[deleted]

Re: Thoughts on Paul Rand

#33
post #8

Discovering someone who is clearly a giant, in a field about which I am ignorant, is my favorite thing about Hacker News. I anticipate good reading ahead: http://www.paul-rand.com/foundation/thoughts/#articles

You're in for a treat. Paul Rand's books like "Design, Form, and Chaos" are great.

Also, the book "Paul Rand" by Stephen Heller is well worth reading.

www.amazon.com/Paul-Rand-Steven-Heller/dp/0714839949

Re: Thoughts on Paul Rand

#34

The only effect I've seen from the word "talent" is to convince some people they'll never be good at anything. I really hate that word and the pretensious jerks who use it.

On the other hand, people who never say anything that pisses someone off probably don't accomplish much of interest.

Re: Thoughts on Paul Rand

#35
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…

"It's arrogant to assume the best way you know how is the best way for the client." That's not what he's saying. He's saying that he's going to try as hard as he can to come up with what he thinks is the best solution to the problem. It may not be the best, but it's the best he can come up with. It's better than someone who comes up with five options, then leaves it up to the client to make the wrong decision. I just…

It's not about pride in your work, it's about the reality of your client. Options normally intend to cover aspects and requirements of the work that the client didn't even think of. Options can allow you to create a solution better than the local maxima that you would find within the confines of your client's understanding of his needs.

Re: Thoughts on Paul Rand

#36
post #4

"At the time I was building a reputation for myself as being a gifted graphical user interface designer." What products has John Maeda designed that we can use or have used in the past? Writing books is great, but its the practical application that really builds reputations.

You'd think someone who lectures design wouldn't have such a crappy blog.

Re: Thoughts on Paul Rand

#37
post #4

"At the time I was building a reputation for myself as being a gifted graphical user interface designer." What products has John Maeda designed that we can use or have used in the past? Writing books is great, but its the practical application that really builds reputations.

You'd think someone who lectures design wouldn't have such a crappy blog.

Or website sorry, wasn't a blog but a website for Asthetics + Computer group at MIT.

Re: Thoughts on Paul Rand

#38
post #35

Earlier quoted context omitted.

"It's arrogant to assume the best way you know how is the best way for the client." That's not what he's saying. He's saying that he's going to try as hard as he can to come up with what he thinks is the best solution to the problem. It may not be the best, but it's the best he can come up with. It's better than someone who comes up with five options, then leaves it up to the client to make the wrong decision. I just…

It's not about pride in your work, it's about the reality of your client. Options normally intend to cover aspects and requirements of the work that the client didn't even think of. Options can allow you to create a solution better than the local maxima that you would find within the confines of your client's understanding of his needs.

I'm not arguing that providing options (done the right way) is a bad way to do it. I'm just disagreeing with someone who says the Paul Rand way of doing things is arrogant. Some people are extremely good at what they do. They have have tons of experience. They do extensive research. And in the end they're able to produce a single solution that endures for decades.

This should be celebrated.

Re: Thoughts on Paul Rand

#39
post #20
post #18

One great story about Paul Rand: "He is one of the most professional people I've ever worked with, in the sense that he thought through all of the formal relationship between a client and a professional such as himself -- obviously very deep thoughts about this -- and therefore he had very clear conclusions about what the relationship meant to both parties and how it should be conducted. For example: I asked him if h…

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. He first made sure he understood their problem.

Re: Thoughts on Paul Rand

#40
Both Maeda and Rand are legends. Ironic that poor design of the ACG site clashed so much with the content of the article.

Notes to self:

    In QA format, place the answers close to the questions they correspond to.

    Be consistent in placing initials before dialog.
Post reply on HN