bquinlan

I'm not surprised about the angle-of-attack needing correction. The angle-of-attack is defined as the angle between the average chord (an imaginary line running from the leading edge of the wing to the trailing edge of the wing) and the relative wind. Since changing the flap position changes the position of the trailing edge, the angle-of-attack will also change.

Back in the day, I was on the team that added Python 2.7 support to App Engine and we were experimenting with a different containment approach.

But Python is a complex language to support - you need to support WSGI, to support dynamic loading (for C extensions), a reasonably performant file system (Python calls `stat` about a billion times before actually importing a file), etc.

So our original runtime was actually Brainf#ck. So, at once point, if you had guessed that Google supported it, you could have written your (simple) webapp in Brainf#ck and Google would have scaled it up to hundreds of machines if needed ;-)

I tried:

  inputs = {
      'matrix': [[10, 20, 30],
                 [5, 5, 10],
                 [2, 2, 1]]
  }
  output = [[85/10, 85/20, 85/30],
            [85/5, 85/5, 85/10],
            [85/2, 85/2, 85/1]]

  tf.cast(tf.divide(tf.reduce_sum(matrix), matrix), 
          tf.float32)

I think that point can support working for either a big company or a small company depending on what type of impact you are looking for.

I've worked for startups in the past and have had a huge impact on the startup but almost no impact on the outside world because the startups just weren't tackling very visible problems.

Now I work for Google and I have basically zero impact on Google i.e. basically nothing that I can do will ever move the dial in terms of Google's revenue, etc. But I've worked on several projects that have had a big impact outside of Google. For example, I was on a small team (3 people) that developed the Python 2.7 runtime for App Engine (this was a while ago) and I was on another small team that implemented the server-side infrastructure for the Google Home. I also developed the screensaver for Chromecast - which is a tiny tiny project - but still millions of people love it.

I enjoyed the write-up but I have a small correction to make about "Frustrating moment #2. You can pass every interview with A grades and still not get a job, because a senior Googler decides that you're the wrong person to be hired."

The author is referring to hiring committees, whose job it is to take the feedback from every interview and make a hire/no-hire decision based on the blended results. I've done hundreds of interviews at Google and I've never seen universally positive interview feedback result in a no-hire decision.

The problem is that most feedback is not universally positive (or negative). So the hiring committee has to dissect the feedback and try to figure out if the identified negatives are (1) credible and (2) sufficient to be disqualifying. That can be pretty difficult (especially if the feedback is contradictory) and why a committee does it rather than the recruiter or hiring manager.

You can also opt to use precise text width measurements (important for Arabic, Chinese, etc.) but then you have to have the font file available on your system.

I disagree with this. The interview that I enjoyed the most was with founders who took me out for beer. We talked a bit about software but most of the discussion was small talk.

After a few months of working there, I realized that some of the people in the office didn't really have any qualifications except "liking beer" and it wasn't a professionally interesting place to work.

My least pleasant interview experience was with Google but I enjoy working there.