Re:When operating "at web scale", users often simply don't h...
by saurik on Monday July 25, 2011 @11:36AM
(#2803009)
I wrote that article, and consider the title I assigned to it here on Hacker News to be its official title; this is also the title that I used when I linked to it on my Facebook Page. Why, therefore, it matters at all that these words "didn't exist anywhere in the article" is beyond me.
As for "buzzwords", if you deal at all with Google employees, this becomes an irritating mantra: systems that have less than a hundred million users are often considered "toys" (and, to be clear, I can totally understand why this would be this way to these people).
And yes: I think that the point that "this actually happens to everyone everywhere" is an interesting point, and was the first comment on this post by patio11. I found that a very interesting insight, as many of my examples are more "those cases that come up when dealing with a global user community full of interesting edge cases", which to me /defines/ "web scale".
Re:When operating "at web scale", users often simply don't h...
by tantalor on Monday July 25, 2011 @11:55AM
(#2803106)
Why, therefore, it matters at all that
these words "didn't exist anywhere in
the article" is beyond me.
What is the purpose of the quotation marks then? Irony?
Re:When operating "at web scale", users often simply don't h...
by saurik on Monday July 25, 2011 @12:04PM
(#2803151)
Yes. Again, that is the official title of the work: imagine that it had been at the top of the linked to page, ironic quotation marks and all.
Re:When operating "at web scale", users often simply don't h...
by innes on Monday July 25, 2011 @12:59PM
(#2803439)
With the benefit of time and reflection, I now think that the term web scale is fine in this context and I was just being a curmudgeon. For what it's worth, which admittedly isn't much!
To reiterate: the number of users (scale) is irrelevant to the issue of problem names.
I can see why someone sprinkled buzzwords on the HN title that didn't exist anywhere in the article, and weren't applicable though. Makes the issue sound more 'techie'.