Live data from Hacker News

Goodbye Google: "Visual Design Lead" leaves Google

stopdesign.com

101–103 of 103 posts

Re: Goodbye Google: "Visual Design Lead" leaves Google

#101
post #100

Earlier quoted context omitted.

> Requiring user testing for shades of blue and thicknesses of border is the height of silliness. No it isn't, if a designers ideas cannot withstand a little objective scientific testing, they aren't worth using. > Moreover, users often don't know they want something until a designer shows them they do. You can never get to those designs by testing blues and borders. Which is the whole point of objective testing, do…

From the way I understood it, he was suggesting that testing for shades of blue and border thickness is nitpicking. An equivalent nitpick more familiar to us would be testing whether using tabs or spaces for code indenting improves coding efficiency.

If it affects conversion, then it's not nitpicking, tabs vs spaces isn't a valid comparison because it can't be so easily measured.

Re: Goodbye Google: "Visual Design Lead" leaves Google

#102
post #87

Earlier quoted context omitted.

I think that's right, but a little overgenerous to engineers. We have our hangups, too. Say, which do you think is better, emacs or vim? Even in a data-driven environment oftentimes the argument gets pushed back from "what to do" to "what to measure."

You can't measure emacs vs vim like you can the effect of color or layout on conversion of an app. When measuring is trivial to do and results are easily seen to directly impact revenue, there's just no excuse to not do it.

I agree. I'm just saying this isn't an "engineer" versus "designer" issue. Engineers have just as many "irrational" opinions as designers.

Emacs vs. Vim, Ruby vs. Python, or whatever.

And those things are quantifiable to some extent. Take a random sample of engineers, give them identical tasks to complete, and vary the editor.

Re: Goodbye Google: "Visual Design Lead" leaves Google

#103
post #64

Earlier quoted context omitted.

It's bad form to diss your employer, current or former, in public. Even more so for a senior guy like that. He's leaving one hot company to go work at another - he can talk about the great opportunity at Twitter. He doesn't need to gripe about the job he's leaving. His post spawned a bunch of mildly unfavorable press, which is currently #1 on Techmeme. Bad form.

Bad form. You keep saying this. Perhaps you'd like to explain why.

Paul Graham once wrote that "unprofessional" was the null criticism. It says nothing other than expresses your distaste. I wonder if "bad form" is the same thing, spoken with a slightly English Public School accent?
Post reply on HN