What is your name?
David de Rosier
What is your preferred email address?
ddrcode@gmail.com
Do you represent a company, institution, consortium, yourself or other entity?
Myself
If you represent a company, institution, consortium, or other entity, please enter it here.
Individual
Why are you interested in joining the Safety Critical Rust Consortium?
Given that I don’t work in safety-critical systems today, the "why" question is a key...
The honest answer is that I’m intentionally moving toward domains where engineering discipline is fundamental. In finance I’ve worked on correctness- and latency-critical systems, often in heavily regulated environments where auditability, traceability, and formal controls are part of everyday engineering. So certification-driven culture isn’t foreign to me - I’m used to building systems that are scrutinized and constrained by external requirements.
What really drives me, though, is designing systems that don’t fail because of hidden assumptions. I care about explicit contracts, determinism, and reducing systemic risk by design. I’m particularly fascinated by the software-hardware boundary: how symbols become signals, and how subtle misunderstandings there can cascade into real-world failures. Safety-critical engineering takes that boundary seriously in a way that resonates with me.
I’m also interested in the exchange in the other direction. The Rust community often leans on memory safety as the main story - which is important, but most mission failures weren’t caused by memory issues. They were caused by ambiguity, mismatched assumptions, and weak contracts. I think there’s a lot Rust engineers can learn from safety-critical culture, and I’d genuinely like to help bridge that gap.
Practically, I’d hope to contribute both technically and publicly. I'm experienced mentor and speaker (Rust, RISC-V), and I’m comfortable helping shape and communicate ideas, not just implementing them.
On experience side, besides my expertise in finance, I'm an ex-academic specialising in parallel systems, with years spent in assembly, low-level C and embedded projects. I'm alse quite familiar with Ada.
That’s why the consortium interests me. It feels like a place where these conversations can happen seriously.
Best,
David
Do you plan to be a producer or observer in the consortium?
Producer
What is your name?
David de Rosier
What is your preferred email address?
ddrcode@gmail.com
Do you represent a company, institution, consortium, yourself or other entity?
Myself
If you represent a company, institution, consortium, or other entity, please enter it here.
Individual
Why are you interested in joining the Safety Critical Rust Consortium?
Given that I don’t work in safety-critical systems today, the "why" question is a key...
The honest answer is that I’m intentionally moving toward domains where engineering discipline is fundamental. In finance I’ve worked on correctness- and latency-critical systems, often in heavily regulated environments where auditability, traceability, and formal controls are part of everyday engineering. So certification-driven culture isn’t foreign to me - I’m used to building systems that are scrutinized and constrained by external requirements.
What really drives me, though, is designing systems that don’t fail because of hidden assumptions. I care about explicit contracts, determinism, and reducing systemic risk by design. I’m particularly fascinated by the software-hardware boundary: how symbols become signals, and how subtle misunderstandings there can cascade into real-world failures. Safety-critical engineering takes that boundary seriously in a way that resonates with me.
I’m also interested in the exchange in the other direction. The Rust community often leans on memory safety as the main story - which is important, but most mission failures weren’t caused by memory issues. They were caused by ambiguity, mismatched assumptions, and weak contracts. I think there’s a lot Rust engineers can learn from safety-critical culture, and I’d genuinely like to help bridge that gap.
Practically, I’d hope to contribute both technically and publicly. I'm experienced mentor and speaker (Rust, RISC-V), and I’m comfortable helping shape and communicate ideas, not just implementing them.
On experience side, besides my expertise in finance, I'm an ex-academic specialising in parallel systems, with years spent in assembly, low-level C and embedded projects. I'm alse quite familiar with Ada.
That’s why the consortium interests me. It feels like a place where these conversations can happen seriously.
Best,
David
Do you plan to be a producer or observer in the consortium?
Producer