1,952 karma · joined February 20, 2007
This latest logo is... I don't have the right words. Looks daycare copy. Welcome to Google. We're not useful, we're safe.
1. Someone (or a group of people) within mistakenly believes this design aesthetic[1] is good and have gained a lot of political power. I guess they like things that look pretty in screenshots instead of things that are actually useful or intuitive?
2. They're heavily optimizing for some metric (engagement, user growth, whatever) that is orthogonal to (or has a small component along) the usability vector.
[1] Simplistic defaults, not easily configurable, flat, tons of whitespace, etc...
Also, not being able to speak well about a past project is highly correlated with doing well on a coding test.
Sounds like one or the other should be thrown out. (Or maybe only the small percentage who do well on both will go on to do well on the job?)
He just stated that his belief is religious...
(Well, he didn't state that exactly, but he did state that you may as well treat it as such.)
This is melodrama. Ignoring the negativity in comments on an internet message board has got to rank as one of the smallest possible challenges a startup can face.
It seems that some bad designers have gained quite a bit of political power within Google somehow.
That image you linked shows that the drop rates for items take into account the existence of the auction house. That sounds like a purely game balance decision. I.e., it would still be true even if only the gold auction house existed.
I never got all the outrage over the existence of the auction houses. In Diablo 2 you'd grind for hours looking for good drops and then have to spam chat rooms and trade with people. In Diablo 3 you'd do the same grinding but just for gold, and then you buy what you need on the auction house with that gold. What's the difference? (Other than in Diablo 3, once you're done grinding its much easier to get what you want.)
You present a reasonable idea. But it's totally orthogonal to the content of the post, so I wish you hadn't made it here.
Interestingly, that article recommends a different book by John Sarno.
This (on top of a bunch of other friction I have with JIRA) makes it clear to me that JIRA is not a product they're building for hackers. It must be for program managers, or for check writers at enterprise companies.