Mike Krieger

The difference between the right context and not, it's entirely the difference between a good answer and a bad answer.

Don't underestimate how much you can think and work like a startup and feel like it's you against the world. It's existential that you go solve that problem and that you go build it... that is a way of working rather than a area of building, but it's a continued advantage if you can harness it.

I always ask it to, if I wanted to use more reasoning, think hard and it'll use a different flow and I usually start with that.

How do we figure out what we want to be when we grow up versus what we currently aren't or wish that we were or see other players in the space being?

I think so much of when you get really metrics obsessed is when you're trying to convince yourself that it is when it's not.

If we're shipping things that could have been built by anybody just using our models off the shelf, there's great stuff to be built by using our models off the shelf by the way, don't get me wrong, but where we should play and what we can do uniquely should be stuff that's really at that magic intersection between the two.

We really rapidly became bottlenecked on other things like our merge queue. We had to completely re-architect it because so much more code was being written and so many more pull requests were being submitted.