No dice. Had to replace the screen. Which I did. Then I returned it for an iPhone SE. And that iPhone has survived much harder drops with no damage whatsoever.

FWIW, having played around with Google's routers, they work pretty well, even from iOS. Chromecasts "just work" in the old Apple sense of the term: you plug it in, you find the thing you want to watch online that you want on your TV, press the button in Chrome and hey presto, you got your cat video on your OLED.

If you're OK with having Google store data on you[1], I'd say the Google hardware division has a lot of what you talk about here.

[1] Before the flood of angry HN replies come in, I get that is not everyone, but knowing what I know about Google's privacy practices, I am perfectly happy with that.

https://4.bp.blogspot.com/-GLc5ve5_djc/V-ysZgW6uDI/AAAAAAAAD...

The worst case scenario was 5x, which was a factor of 10 off. If you are that far off when you do your capacity planning, you can be pretty sure you've got problems throughout your entire stack.

a) I shouldn't ask questions that are in that book, any question found in the wild is banned.

b) I want my candidates to study and show me the best of themselves, and that they want the job and are not wasting my time by throwing their resume on the pile as an afterthought.

c) Cracking the Code Interview is really good at helping you through the algorithmic questions popular on whiteboards. I find the signal:noise ratio on those questions pretty poor, so I ask more straightforward questions that more closely represent things a software engineer encounters in their everyday life. CtCI is good for getting you up to snuff at the stuff you don't do all the time (if ever) just in case you get That Interviewer.

Admittedly, I am but one interviewer and there are many others who do many things many different ways, but I've never heard anyone denounce candidates studying.

Hahaha, please tell me another one Mr. Trump.

> A hiring process that acts as if years of experience mean nothing and which reduces your career to a score on a web page generated by a terrible constructed test is especially flawed and inhumane.

Being old is not an indicator of success.

You seriously seem to live in some wonderland where the quality of a candidate just magically appears out of thin air.

I want candidates to have studied. Studying isn't gaming. Studying is being smart. I want candidates that studied. Those that didn't I don't want. They don't want the job badly enough.

I routinely test older candidates who can't program anywhere outside of the little box they made for themselves, and freak out when they see a programming language that isn't the one they've used for the last 20 years. Is that inhumane?

Gayle is awesome. Cracking the Code Interview is a really great book, and I credit it for getting me through some of my interviews. Everyone here poking at her are people shooting the messenger for delivering the inconvenient truth.

b) If you name the state you think is behind it, you better be ready for the diplomatic repercussions between the US government and the rogue state, as well as potentially stopping doing business in that state (see Google and China)

I'm looking at the postmortem now and without wishing to jump the gun and talk about things I can't, it looks like this is being taken very seriously and a number of improvements and bug fixes are going to result. In this instance, I think it's doing the Cloud Support people a disservice to call them "disingenuous".

Disclaimer: Used to work on Google Cloud, now on Google Open Source Programs Office.

I had better luck with nickel.rs because it has an examples/ folder with quick recipes of most things you'd want to do.

Source: Lived here 10 years.

I think the point still holds. Maybe just not for that one.

Thanks for the bug ticket :)

It's just a pretty terrifying way to output right now.