2 ms·
Old inside joke at Google, you know your project is "important" with two or three other groups are working on exactly the same thing. When I was there, it was d
by ChuckMcM 11y ago
Old inside joke at Google, you know your project is "important" with two or three other groups are working on exactly the same thing. When I was there, it was debated whether or not this selected for the right attributes (it tends to reward groups that execute fast versus ones that execute well). It did not help that some times when they didn't do that (just let one group build it) they didn't always get the result they wanted either.
- jsnell 11y agoThe worst offenders were probably workflow / pipelining systems; just about everyone needed to write sequences of mapreduces, and thought that the existing solutions weren't a perfect fit. IIRC there were at one point over a dozen different workflow systems in use and advertised to at least some degree to other groups, which made picking one even harder due to the paradox of choice. The solution was of course to write a new one.
- thechao 11y agoWhen I studied library design, the situation you described was the basic indicator of "domain misunderstanding": no one understands the domain well enough to produce a suitable abstraction. If the problem persists for a couple of decades, it might imply that domains have been improperly mixed.
- n0us 11y agoThis explains the vast inconsistencies in quality of Google's products and also the feeling I get that none of them ever quite work together the way you would expect.