Skip to content

Comment on Is Google far too much in love with engineering?parent

Comments

Sure, the author is a bit whiny, but I still think he has a point.

One example: design. I still haven't seen a single page from Google that looked stunning, or even good (to my eyes, obviously). Their entire design philosophy seems to be infinite-amount-of-monkeys-hacking-css and A/B-testing. They even manage to make their main landing page, with only a handful of items, look quite messy.

The method may be scientific and all, but it doesn't produce good looks.

Because good looks don't necessarily equate to good performance. They optimize for conversion, not beauty, and make an ass-load more money because of it. That's how it should be done.

You can't really optimize, in the A/B-testing sense, an entire design. You can just tweak the details, in the turd-polishing sense.

That being said, being ugly can of course be profitable. If you want to signal that you are cheap, for example, the ugliness helps. Just look at the difference between, say, Walmart and an Apple store. So maybe Google wants to look cheap - but I for one wish they didn't.

> You can't really optimize, in the A/B-testing sense, an entire design.

That's just crap. You can test anything, including entirely different versions of an app. The idea that you can't test good design is what designers tell themselves to justify their operating on gut feeling and pulling opinions out of their asses.

There isn't anything a user does that you can't come up with a way to test, designers are just afraid of actual data showing them they're full of shit. They don't want their ideas challenged democratically by users, they want their own ideas used instead because of some misplaced sense of taste. Engineers do it right, test, iterate, improve, follow the data wherever it leads regardless of your own ego.

It may be crap, undemocratic, pulled out of behinds, and egotistic. It's still true though.

You can only test a very, very limited number of designs, out of all the pretty much infinitely many possible ones. Someone still has to come up with the designs to test.

And it is very unlikely that you can go from one design to a better one in incremental, A/B-tested steps. It is just as in language: you can test two different novels, for example, but pretty much all the "intermediate novels" you can think of just don't make any sense.

> You can only test a very, very limited number of designs, out of all the pretty much infinitely many possible ones. Someone still has to come up with the designs to test.

Yet it's still testable. There isn't anything you can't test somehow and there isn't any design any designer could come up with that can't benefit from incremental improvement as a result of testing.

> And it is very unlikely that you can go from one design to a better one in incremental, A/B-tested steps.

That's your own strawman, no one says you have to. Test radically different designs against each other, testing will still declare a winner and that winner can be incrementally improved by further testing.

I agree with you, but it is still possible the they are only optimizing within a local minimum (ala Jason Cohen's latest blog post - http://blog.asmartbear.com/local-minimum.html).

I think you're ignoring the fact that a product as familiar as the Google search page alters the search space you're trying to optimize. No matter how bad of an idea it was to add background images, the fuss that it caused was way out of proportion.

Any change that deviates too much from the current state of things has a huge amount of friction working against it. Whatever you think of the current design, I defy anyone to come up with a major overhaul that makes up for the loss of warm fuzzies the average user associates with the current home page.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.