User: Password:
Subscribe / Log in / New account

Quotes of the week

Quotes of the week

Posted Nov 1, 2012 14:49 UTC (Thu) by sumanah (subscriber, #59891)
In reply to: Quotes of the week by jschrod
Parent article: Quotes of the week

I am frankly boggled by your comment. (Your English isn't very good, so that might be part of the problem.)

I read Crystal Beasley's post, and the comments, and she's absolutely not snide at all. Everything she's saying is not only true and respectful, it's not even controversial. In general, coders don't know what to expect from user experience designers: yes. Developers don't have good judgment procedures to know whether proposed designs are correct: yep. And so on for all of her points.

If you think there's an additional point to add regarding high-handed designers who don't listen or collaborate effectively, you haven't actually read the post, in which she says: "The solutions to all these problems lie in communication and building a trusted relationship. It’s a higher barrier for designers that takes time to overcome. I've found all of my team to be receptive when I've taken the time to explain the principles that guide my decisions." How in the world is that snide, or trivializing the problem?

(Log in to post comments)

Quotes of the week

Posted Nov 1, 2012 15:22 UTC (Thu) by raven667 (subscriber, #5198) [Link]

The comment in particular that the OP is responding to is this one, from the comments section on the blog:

>>“representing the work of a designer requires a shift in culture of the dev team”

>BS. A gigantic and stinking pile of BS.
>Becoming _part_ of a dev team requires a shift in culture *of the designed*.
>Designers should stop thinking that they lead or guide the dev team. Make your _proposals_ in a >humble and collaborative language and you will be heard, like everybody else. Try to impose your >“vision” from high in the sky and you will be… ignored. It’s that simple.

This comment seems to match the thinking of the OP. It asserts that designers should not bring their professional knowledge to the dev team, should not bring vision or guidance but should instead be humble in the presence of developers. I don't know whether this is supposed to be sexist or elitist but it's not a successful collaboration strategy.

Quotes of the week

Posted Nov 1, 2012 18:27 UTC (Thu) by dlang (subscriber, #313) [Link]

ANYONE who joins a project and starts off with

> I am an expert, you must listen to me, and you don't know enough to even question my direction

is going to be ignored.

It doesn't matter if this person is a designer, a coder, a DBA, or a networking person. That attitude just doesn't fir with open projects.

You need to become part of the project, make small suggestions first, and back up your suggestions with reasons for them to be implemented (not just "because I say so and I'm the expert")

Unfortunantly, many designers do take the attitude that other people aren't qualified to question their design.

This is not saying that they are being asked to be humble in the presence of the mighty developers, it's asking them to be humble in the presence of the established team, just like a new developer would need to be.

Quotes of the week

Posted Nov 1, 2012 18:49 UTC (Thu) by raven667 (subscriber, #5198) [Link]

And that's pretty much what Crystal Beasley's blog post says. The conflict is where a developer is taking the same attitude that you are ascribing to designers, namely that:

> I am an expert, you must listen to me, and you don't know enough to even question my direction

which doesn't work either.

Quotes of the week

Posted Nov 2, 2012 6:24 UTC (Fri) by viro (subscriber, #7872) [Link]

The trouble is, I *can* explain the reasoning behind technical arguments. From the first principles, if needed. And I'm yet to meet an UI designer who would be willing to do the same. References to earlier work are fine - that's not a problem. As long as you are willing to reproduce the reasoning in those works *and* answer the questions without cyclical arguments. Failure to do so earns you the same respect I'd grant to Feng Shui crowd - sure, many of their suggestions are sane (and quite a few are plain common sense), but unless they can somehow demonstrate that qi exists, well...

Quotes of the week

Posted Nov 5, 2012 12:15 UTC (Mon) by hummassa (subscriber, #307) [Link]

Good designers also can explain the reasoning behind design arguments. And design principles are not qi; they are usually backed up with science, user testing and painstakingly many statistical treatments. Many times design school is science-y then coding courses.

Designers and developers should learn as a principle to understand and respect each other. This includes both knowing when and how to explain each one's arguments and when to stop short of the "go learn to code" or "go learn to design" shoutmatch.

Quotes of the week

Posted Nov 5, 2012 19:05 UTC (Mon) by dlang (subscriber, #313) [Link]

The problem is that there are very few good designers around :-)

to be fair, there are very few good programmers around as well, but the ones who aren't good tend to get weeded out rater quickly in successful opensource projects (and they stand out by comparison with the good ones)

There are so few designers who try to get involved in opensource projects that it's hard to make comparisons between them.

Copyright © 2018, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds