I'd be happy to get you into the interview process, or at least point you in the right direction.
My experience at Amazon has been great. I don't know anyone who cries at their desk, works 80 hours per week, or feels like they're being pushed through a meat grinder. I worked for Microsoft before Amazon, and that was brutal. You'll find bad teams at every large company. One of my friends was on one at Google.
I'd take you up on that offer. I'd love to have a third crack at it.
I've had two coding challenges within that last year. One for an internship and one for a full time position (earlier today no reply yet don't expect one). The problem for me is I freeze. As soon as the "testing" type pressure gets put on I go cold and freeze. Then as soon as the test is over I can pull alllllll the information forward. It sucks because I struggle with CS exams too. Every time I have a test I freeze until I'm out of time and as soon as I leave a room it all comes back.
I'd love to have a go at the interview process if it's possible. I had an interview process a while back (at the end of April I believe) but I don't know what went wrong -
I kept getting calls from Amazon (Seattle number) claiming I had not done the test (which I had already done) and the HR folks mentioning I was not selected - and to try 6 months later.
I would definitely like to have another go at it, if possible.
Where do you live? In Vancouver, Earls and Joeys don't have pictures on their menus. Red Robins and BP do, but they're definitely a tier below the former two.
Thanks for posting this. In the future, could you please add the algorithm to the title? This feels a couple steps removed from clickbait. No offense intended; it's just a suggestion.
> Babai has declined to speak to the press, writing in an email: “The integrity of science requires that new results be subjected to thorough review by expert colleagues before the results are publicized in the media.”
I'm okay with Quanta Magazine leaving out the irony; I can imagine the Engadgets and Buzzfeeds of the world would omit his response and draw their own wild conclusions regardless.
For the nearly all practical purposes, there already exist efficient algorithms for GI. This work is mostly of interest for theoretical matters because it shows that GI can be solved in quasi-poly time for _all_ graphs, whereas previous work still had exponential time worst-cases. Hence why there isn't really a concise algorithm that you'd want to implement.
I love this, it's refreshing. Every time something goes down, I see a flood of hate and a torrent of comments suggesting everyone move somewhere else. That, coupled with HN's hate of MSFT, makes this one of the most refreshing posts I've seen in some time. And sensible.
Where in Canada are you? I haven't seen a single Blackberry at UBC. The iPhone dominates and there's quite a few Android phones around, but virtually nothing else.
Edit: It's worth noting my buses often pick up dozens of high school kids as well, and again, I'm not seeing Blackberry. Maybe it's bigger in Toronto?
I'm in Victoria - my class (all programmers) are about evenly split between Android and Blackberry, with one or two iPhones. Before midterm die-off last year, when 1/3 of our class dropped out, there were more Blackberries. In my household, which consists of 3 Uvic varsity athletes and me, the nerd, there's a 50/50 split between Blackberry and iPhone. I'm a Blackberry user myself, and me and the others who have them are pretty darn loyal. I don't need 24/7 web access. All I need is email and the ability to text without wanting to die of irritation.
It might be worth considering that some people just work/study so much that a normal relationship just isn't going to happen. I imagine grad school and early startup life is like this, to some extent. Personally, I just don't balance my life that well; too much time goes into studying and hacking.
A "pickup artist" did math similar to this and concluded guys should spend very little time on girls that aren't interested in them, as it's emotionally taxing and numerically daft.
It's a good intermediate companion to the official Rust intro [1]. I found it most helpful when reading third-party crates.
[0] https://github.com/dtolnay
[1] https://doc.rust-lang.org/stable/book/