Berk Yilmaz

Of course.

And first of all, thank you.

I'm glad to be here, Brian.

And, you know, looking back, the thread was actually pretty simple.

I kept up ending in places where software failure wasn't an option.

And the tooling actually never matched the stakes.

For example, at NGIT and Istanbul Technical University, I was splitting time between electrical engineering and computer sciences, which sounds a little scattering, but it gave me something that is important.

I learned to think about the software the way hardware engineers do.

You don't ship circuit board and hope it actually works.

You verify it, you prove it.

And that mind stack actually stuck with me through my whole university life.

And Columbia actually depended that.

And then NASA research really finalized this

pushback.

And when you're working on systems that might end up in space where you can just push the hotfixes, you learn the fast that the gap between that it compiles and it's actually correct.

It's just enormous.

And most developer tools just don't care about this gap.

And that's, that's what led to Sentinel.

At NOAA Labs, we're building the development environment

for engineers who work on software where the consequences of getting wrong is actually real.