Matthias Endler

How big is the codebase, the Rust codebase?

And that was developed by how many people? What's the team size?

And that was developed by how many people? What's the team size?

And that was developed by how many people? What's the team size?

Yeah, very nice. A very substantial code base, but also, I would say, still manageable. So I would assume a lot of work also went into speccing out things, creating architecture diagrams, making sure that everything is wired up correctly, communication and so on. There's a lot of complexity introducing a completely new toolchain, new language, everything.

Yeah, very nice. A very substantial code base, but also, I would say, still manageable. So I would assume a lot of work also went into speccing out things, creating architecture diagrams, making sure that everything is wired up correctly, communication and so on. There's a lot of complexity introducing a completely new toolchain, new language, everything.

Yeah, very nice. A very substantial code base, but also, I would say, still manageable. So I would assume a lot of work also went into speccing out things, creating architecture diagrams, making sure that everything is wired up correctly, communication and so on. There's a lot of complexity introducing a completely new toolchain, new language, everything.

How long until they are fully ramped up?

How long until they are fully ramped up?

How long until they are fully ramped up?

So it's a bit of a myth that the Rust learning curve is a huge problem for people that want to work with Rust professionally.

So it's a bit of a myth that the Rust learning curve is a huge problem for people that want to work with Rust professionally.

So it's a bit of a myth that the Rust learning curve is a huge problem for people that want to work with Rust professionally.

And how did you learn how to write idiomatic Rust? Do you have any coding guidelines? Did you talk to the people from Grappit on how to write idiomatic Rust? Are there any resources that you maybe recommended to your team?

And how did you learn how to write idiomatic Rust? Do you have any coding guidelines? Did you talk to the people from Grappit on how to write idiomatic Rust? Are there any resources that you maybe recommended to your team?

And how did you learn how to write idiomatic Rust? Do you have any coding guidelines? Did you talk to the people from Grappit on how to write idiomatic Rust? Are there any resources that you maybe recommended to your team?

And when I would be tasked with building code for cars, I would be extremely defensive because I know that I wouldn't be able to just connect to the car or maybe have a shell connection and just troubleshoot on the live machine. These cars, they run for years and sometimes they have to go without maintenance or people don't do those updates that regularly as they should.

And when I would be tasked with building code for cars, I would be extremely defensive because I know that I wouldn't be able to just connect to the car or maybe have a shell connection and just troubleshoot on the live machine. These cars, they run for years and sometimes they have to go without maintenance or people don't do those updates that regularly as they should.

And when I would be tasked with building code for cars, I would be extremely defensive because I know that I wouldn't be able to just connect to the car or maybe have a shell connection and just troubleshoot on the live machine. These cars, they run for years and sometimes they have to go without maintenance or people don't do those updates that regularly as they should.

So how defensive is the code? How, let's say, painstaking is it to work with inputs and outputs? How does the error handling story look like? Is it... Would it be normal Rust code that people could understand or is it very specific Rust code?