Matt Van Itallie

We run the analytics, produce a CSV and build it by hand, usually for a month or two, because that's, of course, not at all scalable. Number one, it saves a huge amount of engineering time. And number two, you really have to be sure you're building the right thing.

We run the analytics, produce a CSV and build it by hand, usually for a month or two, because that's, of course, not at all scalable. Number one, it saves a huge amount of engineering time. And number two, you really have to be sure you're building the right thing.

And it's a mark of success for us that we run into scalability issues that then need to be solved with better, with a different architecture, different engineering approach, etc. The absence of running into scale issues would itself be worrisome for us.

And it's a mark of success for us that we run into scalability issues that then need to be solved with better, with a different architecture, different engineering approach, etc. The absence of running into scale issues would itself be worrisome for us.

And it's a mark of success for us that we run into scalability issues that then need to be solved with better, with a different architecture, different engineering approach, etc. The absence of running into scale issues would itself be worrisome for us.

The team and the trust-based relationships with our customers and partners. The team side, I just could not be more proud that folks, most of whom we've never met, we are a global team and have really come together to have one and one equal three or more. So many different backgrounds, so many different experiences, but all marching in the same direction to build something that matters.

The team and the trust-based relationships with our customers and partners. The team side, I just could not be more proud that folks, most of whom we've never met, we are a global team and have really come together to have one and one equal three or more. So many different backgrounds, so many different experiences, but all marching in the same direction to build something that matters.

The team and the trust-based relationships with our customers and partners. The team side, I just could not be more proud that folks, most of whom we've never met, we are a global team and have really come together to have one and one equal three or more. So many different backgrounds, so many different experiences, but all marching in the same direction to build something that matters.

And then what we do, as we say in our work, the code of a company is the second most important thing they have after the people. And we've had a trillion dollars of organizations trust us to scan their code. And that is such an honor from our clients or our partners to code owners, because we frequently are involved in technical due diligence.

And then what we do, as we say in our work, the code of a company is the second most important thing they have after the people. And we've had a trillion dollars of organizations trust us to scan their code. And that is such an honor from our clients or our partners to code owners, because we frequently are involved in technical due diligence.

And then what we do, as we say in our work, the code of a company is the second most important thing they have after the people. And we've had a trillion dollars of organizations trust us to scan their code. And that is such an honor from our clients or our partners to code owners, because we frequently are involved in technical due diligence.

That is just an unbelievable statement of trust that we work every day to earn and re-earn. I am just so proud of the team for building something that matters enough and has earned the trust of organizations like the ones that we serve.

That is just an unbelievable statement of trust that we work every day to earn and re-earn. I am just so proud of the team for building something that matters enough and has earned the trust of organizations like the ones that we serve.

That is just an unbelievable statement of trust that we work every day to earn and re-earn. I am just so proud of the team for building something that matters enough and has earned the trust of organizations like the ones that we serve.

The mistake that comes foremost to mind is a product roadmap decision that I made with I directed the team, guided the team to build more of a robust set of functionality than really was necessary to get to product market fit. We were going too broad when we should have gone deeper. The evidence of that was in the growth rate of the first product, which is to say it was not growing enough.

The mistake that comes foremost to mind is a product roadmap decision that I made with I directed the team, guided the team to build more of a robust set of functionality than really was necessary to get to product market fit. We were going too broad when we should have gone deeper. The evidence of that was in the growth rate of the first product, which is to say it was not growing enough.

The mistake that comes foremost to mind is a product roadmap decision that I made with I directed the team, guided the team to build more of a robust set of functionality than really was necessary to get to product market fit. We were going too broad when we should have gone deeper. The evidence of that was in the growth rate of the first product, which is to say it was not growing enough.

And the solution was to radically simplify. We basically lopped off a big chunk of that product just so we could focus on a core part that we were pretty sure customers would really value. Thankfully, it turns out we were right, then continued to build that product, that CodeScan's product, based on a much smaller but much firmer foundation than what we'd initially been building.

And the solution was to radically simplify. We basically lopped off a big chunk of that product just so we could focus on a core part that we were pretty sure customers would really value. Thankfully, it turns out we were right, then continued to build that product, that CodeScan's product, based on a much smaller but much firmer foundation than what we'd initially been building.

And the solution was to radically simplify. We basically lopped off a big chunk of that product just so we could focus on a core part that we were pretty sure customers would really value. Thankfully, it turns out we were right, then continued to build that product, that CodeScan's product, based on a much smaller but much firmer foundation than what we'd initially been building.