This is one thing Apple really 'got right' in iOS. You can especially see it in any app that allows you to zoom or pan the view. If you change the perspective, it will always redraw the screen according to your input. Sometimes it has to fill in the new area with a temporary texture while it runs off to load the right one, but the response is instantaneous.
As an Android user, this is one of my biggest gripes. Android just hasn't figured this out, yet, or doesn't care.
I think that Android started off the wrong way with something aimed at the existing competition at that time (so the first Blackberry, WP and Nokia smartphones).
Now it is very hard to revamp Android in order to accomplish this.
I just hope that the experiments made by the Dart team (they are aiming at a 120 fps lag free framework on Android) are also conducted internally in the Android team (not necessarily with Dart, but preferably not with Java).
There are lots of big companies with a great reputation for treating their employees well (e.g., Facebook, Google), but also plenty that grind them into the ground and spit them out. Apple, perhaps, being the most commonly referenced.
The article only briefly mentions Carl Sagan and how he coined the name, "Pale Blue Dot". If you haven't read or listened to where this came from in Carl Sagan's "Cosmos", it is a very beautiful and poignant reflection on humanity.
The docs and interface look great, and it's nice that each one comes with a sort of mini-walkthrough.
If any Google devs read this, I do have one request: it would be awesome to see runtime analysis based on the theory / design of the provided code, with perhaps some explanation of why certain design decisions were made in the solution.
It's already an excellent educational tool, and this seems like an easy way to make it even better.
If successful, it will be interesting to see how Chrome evolves for developers to compete.
(I was reminded of this because the Firefox sidebar was always wildly popular - I know lots of people that continue to use it specifically for that purpose)
The author definitely stressed this a few times in the article.
To a new employer, the fact that he "made it through a Google interview" honestly doesn't mean much. Even Google interviews are wildly variable, and more importantly it doesn't in any way indicate that the candidate is a good match for whatever job he/she is interviewing for.
Talking about products and designs he had worked on in the past, at a technical level, though, is crucially important, and the author also pointed out they failed to do that (or at least I think he did?)
Anyway, getting a job at "one of the big employers" honestly doesn't mean much - there are plenty of people that get rejected that probably deserved a hire, and plenty of of people that get hired that aren't up to par. What matters more is what the candidate did while he was there.
It's sort of funny that he points out how broken interviewing & hiring is, but then also says that because he got hired by Google, he should be treated differently.
