Sebastian Scholz

And I mean, it came out clearly on top.

The memory safety, just eradicating a whole bunch of errors that you can have with C and C++ is really critical for space applications.

It's these kind of avoidable errors that can be caught before you deploy your code.

That can just be denied by the compiler.

And in general, the help that the compiler gives you compared to other languages in writing safe and good code, this I think was the main driver.

And of course, the ability to still go into the embedded systems level, still be real-time and be reliable.

Yeah, actually, it's very, very similar.

So in a bunch of companies, you would find setups with GitLab, for example, and so do we have it.

We use a lot of crates that are just out there for many people to use, like ZeroCopy, for example, and other things, ProbeIS for our debugging environment.

It's a little bit more specific because we work with hardware.

So in many software companies, you have your code, you have unit tests, you have integration tests that you run on your CI, and that's that.

We have to interface with actual real hardware.

And so maybe one of the key differences is that we have a flat set of

for the Gamma Alpha product, for the Gamma Alpha satellite.

FlatSat, I should say, is basically the electronics of the satellite unwrapped, laid out on a flat on a table.

Hence the name FlatSat.

And it's a one-to-one, pretty much a one-to-one copy of the actual hardware of the satellite.

And we integrated it in our CI so that our tests, we have mainly integration tests, and they run on the actual hardware.

And then we have probes attached to look at the actual output of the system and make sure that everything's all right.

Yeah, it took us a while to get all of these systems up and running.