Matt Van Itallie

And when I was satisfied I had a good enough technology base, I was very fortunate to meet my co-founder, and we've been doing it for the seven years since. It is hard to summarize code, so we really have spent years making it useful for our first product, making our first product useful across 40-plus languages in a detailed way, and all languages at least to be able to say something about it.

And so that's been a huge part of our journey and that's our code scans product. And then about a year ago, incredibly fortunate that some of our major customers asked us to build something new and there's no more magical way to get to product market fit than being asked, being asked by your customers to build it.

And so that's been a huge part of our journey and that's our code scans product. And then about a year ago, incredibly fortunate that some of our major customers asked us to build something new and there's no more magical way to get to product market fit than being asked, being asked by your customers to build it.

And so that's been a huge part of our journey and that's our code scans product. And then about a year ago, incredibly fortunate that some of our major customers asked us to build something new and there's no more magical way to get to product market fit than being asked, being asked by your customers to build it.

We've also started building and have built a product to help coders and help engineering teams manage how much gen AI code is in their code base. So you can think of it like an ingredients list. How much was Gen AI code? How much was human? How much was a mix? And that has been, you know, just, I say grateful and fortunate a lot, but man, it is true.

We've also started building and have built a product to help coders and help engineering teams manage how much gen AI code is in their code base. So you can think of it like an ingredients list. How much was Gen AI code? How much was human? How much was a mix? And that has been, you know, just, I say grateful and fortunate a lot, but man, it is true.

We've also started building and have built a product to help coders and help engineering teams manage how much gen AI code is in their code base. So you can think of it like an ingredients list. How much was Gen AI code? How much was human? How much was a mix? And that has been, you know, just, I say grateful and fortunate a lot, but man, it is true.

Just to be able to work on two really important topics to help improve code, help support coders, help businesses and organizations achieve better outcomes through code is an incredible gift.

Just to be able to work on two really important topics to help improve code, help support coders, help businesses and organizations achieve better outcomes through code is an incredible gift.

Just to be able to work on two really important topics to help improve code, help support coders, help businesses and organizations achieve better outcomes through code is an incredible gift.

Let's really tell the truth here. I probably researched a way to analyze the architecture of code automatically. That probably took two years of reading journal articles. I was making a tech transfer play. I thought that there might be some high quality IP at a university that we could use to build our first product. After that two years, we found something.

Let's really tell the truth here. I probably researched a way to analyze the architecture of code automatically. That probably took two years of reading journal articles. I was making a tech transfer play. I thought that there might be some high quality IP at a university that we could use to build our first product. After that two years, we found something.

Let's really tell the truth here. I probably researched a way to analyze the architecture of code automatically. That probably took two years of reading journal articles. I was making a tech transfer play. I thought that there might be some high quality IP at a university that we could use to build our first product. After that two years, we found something.

I'm proud to say that some great research conducted by a professor from the University of Michigan is still part of our product. Once we had that IP lockdown, I'd say it was about eight months to the first MVP. Over time, SEMA has gotten better and better at building MVPs faster, but probably about eight months from business origination to first product.

I'm proud to say that some great research conducted by a professor from the University of Michigan is still part of our product. Once we had that IP lockdown, I'd say it was about eight months to the first MVP. Over time, SEMA has gotten better and better at building MVPs faster, but probably about eight months from business origination to first product.

I'm proud to say that some great research conducted by a professor from the University of Michigan is still part of our product. Once we had that IP lockdown, I'd say it was about eight months to the first MVP. Over time, SEMA has gotten better and better at building MVPs faster, but probably about eight months from business origination to first product.

So first in terms of the technical debt trade-off, I do actually think we got this one. The more advanced you are on product market fit, the more advanced you are on the state of your business, the the more that non-functional requirements really matter. Up to the major companies, of course, where you really have to get code quality and security and open source risk locked down.

So first in terms of the technical debt trade-off, I do actually think we got this one. The more advanced you are on product market fit, the more advanced you are on the state of your business, the the more that non-functional requirements really matter. Up to the major companies, of course, where you really have to get code quality and security and open source risk locked down.

So first in terms of the technical debt trade-off, I do actually think we got this one. The more advanced you are on product market fit, the more advanced you are on the state of your business, the the more that non-functional requirements really matter. Up to the major companies, of course, where you really have to get code quality and security and open source risk locked down.

But we really had an intentional approach. One of two of SEMA's five values are scrappiness, which means for us solving for a trade-off of quality and speed, and excellence, which is just optimizing quality. A big part of SEMA is continuously asking questions