Matthias Endler

For example, Sardi, would it show up somewhere? Yeah, it would show up, definitely. Okay.

Let's say I started Volvo and I'm in your team and I want to start working on this project in Rust. What would my day-to-day look like? I plug myself into an embedded device? Certainly not. There's probably some other device somewhere I need authentication for. And then we have some CICD process. We have ProBias somewhere in the tool chain. We have an IDE.

Let's say I started Volvo and I'm in your team and I want to start working on this project in Rust. What would my day-to-day look like? I plug myself into an embedded device? Certainly not. There's probably some other device somewhere I need authentication for. And then we have some CICD process. We have ProBias somewhere in the tool chain. We have an IDE.

Let's say I started Volvo and I'm in your team and I want to start working on this project in Rust. What would my day-to-day look like? I plug myself into an embedded device? Certainly not. There's probably some other device somewhere I need authentication for. And then we have some CICD process. We have ProBias somewhere in the tool chain. We have an IDE.

And then we have a build process in the end. And eventually... There will be a binary and a software bill of materials and probably some sort of integration of all the components later on. So walk us through all the steps.

And then we have a build process in the end. And eventually... There will be a binary and a software bill of materials and probably some sort of integration of all the components later on. So walk us through all the steps.

And then we have a build process in the end. And eventually... There will be a binary and a software bill of materials and probably some sort of integration of all the components later on. So walk us through all the steps.

Nice.

Nice.

Nice.

What's so special about Zool? Because not many people might know it.

What's so special about Zool? Because not many people might know it.

What's so special about Zool? Because not many people might know it.

Isn't it also true that we're dealing with embedded devices here? I know roughly how that would work for a backend service, say. But for embedded devices, I would be scared that the device would be in a weird limbo state or... wasn't completely flashed when the test ran. So how do you ensure that the tests are always correct and start from a deterministic position?

Isn't it also true that we're dealing with embedded devices here? I know roughly how that would work for a backend service, say. But for embedded devices, I would be scared that the device would be in a weird limbo state or... wasn't completely flashed when the test ran. So how do you ensure that the tests are always correct and start from a deterministic position?

Isn't it also true that we're dealing with embedded devices here? I know roughly how that would work for a backend service, say. But for embedded devices, I would be scared that the device would be in a weird limbo state or... wasn't completely flashed when the test ran. So how do you ensure that the tests are always correct and start from a deterministic position?

How long does a typical build take?

How long does a typical build take?

How long does a typical build take?

And that includes setting up all the devices and running the integration test?