Adam Jacob

It just takes time to understand what the actual outcomes of any individual engineering choice or any individual product feature would be. We have to figure out how to teach people to be the best athlete that they can be. In the case of a software engineer, if you think about them the same way you would think about someone on a basketball team, like you gotta train them. I have to drill them.

It just takes time to understand what the actual outcomes of any individual engineering choice or any individual product feature would be. We have to figure out how to teach people to be the best athlete that they can be. In the case of a software engineer, if you think about them the same way you would think about someone on a basketball team, like you gotta train them. I have to drill them.

I have to give them feedback all the time. I have to be present and talk about their career growth and talk about what makes them a great engineer and what makes them unique as an engineer. And then you gotta figure out how that plays with the other people that they work with in the team. And how do we keep their ability to play the game

I have to give them feedback all the time. I have to be present and talk about their career growth and talk about what makes them a great engineer and what makes them unique as an engineer. And then you gotta figure out how that plays with the other people that they work with in the team. And how do we keep their ability to play the game

I have to give them feedback all the time. I have to be present and talk about their career growth and talk about what makes them a great engineer and what makes them unique as an engineer. And then you gotta figure out how that plays with the other people that they work with in the team. And how do we keep their ability to play the game

and keep the context coming to them that they need about how the tactical work that you're asking them to do attaches to that strategic work that's on that roadmap. And so that's how I think about building teams. I think about them literally like I'm assembling a team of professional experts. And what I'm going to do is train them to be the best possible version of themselves they can be.

and keep the context coming to them that they need about how the tactical work that you're asking them to do attaches to that strategic work that's on that roadmap. And so that's how I think about building teams. I think about them literally like I'm assembling a team of professional experts. And what I'm going to do is train them to be the best possible version of themselves they can be.

and keep the context coming to them that they need about how the tactical work that you're asking them to do attaches to that strategic work that's on that roadmap. And so that's how I think about building teams. I think about them literally like I'm assembling a team of professional experts. And what I'm going to do is train them to be the best possible version of themselves they can be.

And then I'm going to put them on teams where I'm situating people by looking at their strengths and weaknesses and trying to figure out how do I build the strongest possible team to attack these problems.

And then I'm going to put them on teams where I'm situating people by looking at their strengths and weaknesses and trying to figure out how do I build the strongest possible team to attack these problems.

And then I'm going to put them on teams where I'm situating people by looking at their strengths and weaknesses and trying to figure out how do I build the strongest possible team to attack these problems.

Look, there's always pinch points around scale. It doesn't matter who you are or how good you are at the job. You'll just scale will always be painful because there's no real substitute for production load when it comes time to tell you how complex distributed system will work under pressure.

Look, there's always pinch points around scale. It doesn't matter who you are or how good you are at the job. You'll just scale will always be painful because there's no real substitute for production load when it comes time to tell you how complex distributed system will work under pressure.

Look, there's always pinch points around scale. It doesn't matter who you are or how good you are at the job. You'll just scale will always be painful because there's no real substitute for production load when it comes time to tell you how complex distributed system will work under pressure.

One of the things that we've had to do in order to make this work is we built that big hypergraph of functions that I mentioned at the top. That thing is literally like a big in-memory graph and the speed of the operations that you can do on that graph and the speed with which we can then recalculate those functions.

One of the things that we've had to do in order to make this work is we built that big hypergraph of functions that I mentioned at the top. That thing is literally like a big in-memory graph and the speed of the operations that you can do on that graph and the speed with which we can then recalculate those functions.

One of the things that we've had to do in order to make this work is we built that big hypergraph of functions that I mentioned at the top. That thing is literally like a big in-memory graph and the speed of the operations that you can do on that graph and the speed with which we can then recalculate those functions.

So if you imagine I change a property that then could change hundreds or thousands of other things. How do you calculate what's going to change? Then you need to execute all the functions in the right order. And then you need to apply all of those things back to this big graph so that when I display it to the user, that happens.

So if you imagine I change a property that then could change hundreds or thousands of other things. How do you calculate what's going to change? Then you need to execute all the functions in the right order. And then you need to apply all of those things back to this big graph so that when I display it to the user, that happens.

So if you imagine I change a property that then could change hundreds or thousands of other things. How do you calculate what's going to change? Then you need to execute all the functions in the right order. And then you need to apply all of those things back to this big graph so that when I display it to the user, that happens.