Matthias Endler

So I'm guessing you develop code in your IDE.

I'm not sure which IDE you use.

Oh, wow.

That's a really cool project in and of itself because I really wondered how would you test your hardware components?

You kind of want to abstract that away.

You don't want to unplug and plug it back in again.

You kind of want to have a system for that.

And I'm assuming that there's not much on the market, especially for flat sets like this.

It's probably still an embedded setup, just like any other embedded setups, but...

The moment you go into the details here, you will find that you probably need a custom solution, right?

But the integration tests are still in a tests folder, just like you would expect from any normal ROS project, right?

Now, earlier you mentioned correctness in a different context, but I think it fits in here as well, because couldn't you test a lot of the logic with unit tests?

Or is it so that you kind of want to always test the inputs and outputs as well, because it's kind of a monolithic service?

When you say that you store files on Flash...

In a normal scenario, it wouldn't be a problem if the flash storage fails.

You can't just fix it because it's maybe right next to you, but it's harder to do in space.

Do you have any failover for that sort of hardware failure?

And if so, how do you test that?

Let's talk a little bit about your background, where you came from.

what your other strong languages were, and how you got onboarded on the project and your first experiences with the code base.