3 ms·
I know some of those Android engineers, and I've also done (and loathed) Android development, and I do think they are some of "the smartest engineers on the pla
by nostrademons 10y ago
I know some of those Android engineers, and I've also done (and loathed) Android development, and I do think they are some of "the smartest engineers on the planet". The only problem is that they're optimizing for their success, not yours (which, if they're smart, is exactly what they would be doing).
At Google, you get promoted for launching something that is technically difficult. So most engineers will seek to implement the most technically difficult feature they have a chance of launching, and then do everything they can to ensure that it actually launches. Nobody gets promoted for not launching things and ensuring API stability. Nobody gets promoted for fixing bugs their managers doesn't know about. Few people get promoted for writing documentation (and if you do, you're probably a techwriter who doesn't call the shots on API design). Nobody gets promoted for doing mundane stuff that might improve the user experience, but isn't technically difficult.
It's the standard big-company modus operandi: hire the best, and incentivize them in ways where it's easy to define the incentives but those incentives don't necessarily add value to the customer. Usually by the time you get to that size, it doesn't matter anyway, since you're working on problems that no startup has the resources to tackle.