yes -- i was given a media package
yes -- i did go ahead and hollow it out and go out of my way to include our little Ferris for the Safety-Critical Rust Coding Guidelines :)
yes -- i was given a media package
yes -- i did go ahead and hollow it out and go out of my way to include our little Ferris for the Safety-Critical Rust Coding Guidelines :)
announcement image reading: I am speaking at #ACC US 2026 with a picture of Pete LeVasseur and his name and Woven by Toyota.
hey -- anybody coming out to Automotive Computing Conference US in Detroit on March 24th, 25th?
i'll be there chatting about "why Rust in safety-critical systems" in back-to-back sessions with @skade.bsky.social of @ferroussystems.bsky.social
come say hi! let's chat about blockers
check out the playlist of other interviews we've conducted so far:
www.youtube.com/watch?v=r7i-...
shout out to @tylermandry.bsky.social for performing the interview and in such a scenic spot!
splash screen of interview of Daniel Almeida on work in writing a Linux GPU kernel driver in Rust
wanna hear about what writing a Linux GPU kernel driver is like?
how about what it's like _in Rust_?
check out the interview of Daniel Almeida!
another production of the Rust Project Content Team โ๏ธ
the page to nab the .ics to get the meeting on your calendar is here:
github.com/rust-sig/rus...
listing of talks coming up are here:
github.com/rust-sig/rus...
in two weeks at the next Rust SIG i'll go through the blog post i wrote as a member of the Rust Vision doc team on: "What does it take to ship Rust in safety-critical?"
- and some things were left on the cutting room floor when writing it!
blog.rust-lang.org/2026/01/14/w...
if you weren't able to make it this time to the @sdv.eclipse.org 's Rust Special Interest Group, feel free to check out the meeting notes below:
github.com/orgs/rust-si...
screenshot showing that we had Daniel Silverstone of Codethink out to share with us about gaps between C and Rust when it comes to high-assurance and safety-critical
thanks to Daniel Silverstone of @codethink.co.uk for coming out to share C <=> Rust gaps when it comes to high-assurance and safety-critical at the @sdv.eclipse.org Rust Special Interest Group
> me, sleeping 8 hours, even interrupted here and there
wtf, sleeping helps?
i was always an early riser, had given up on being an early sleeper
maybe gotta revisit that D:
Do I know anyone who's worked with LittleFS for embedded devices? I'm writing some Rust tooling for building and deploying it and would appreciate hearing about how others have used it!
until you write it all in Rust tbh
we all believe in you!
if you're a part of an organization using Rust in automotive and/or another regulated industry and would like to talk about it in a low-stakes "watercooler chat" format in the Eclipse SDV Rust SIG feel free to reach out :)
you can see more of our upcoming Eclipse SDV Rust SIG watercooler chat-style talks on the schedule here
github.com/rust-sig/rus...
attending is easy, go here to pick up the .ics and add it to your calendar
github.com/rust-sig/rus...
we had a good deal of interest on Rust in Functional Safety in our last Rust SIG meeting, which got me talking with Alex Senier of Ferrous Systems to come out. seems like that'll happen in May, so keep an eye out for it
screenshot showing upcoming Eclipse SDV Rust SIG talks in particular, tomorrow's / March 3rd 2026's is highlighed: "Measuring the gap between C and Rust" by Daniel Silverstone of Codethink
in ~23 hours see the work that Daniel Silverstone from @codethink.co.uk has done in C <=> Rust gap analysis at the @sdv.eclipse.org Rust SIG meeting :D
9 y/o and 6 y/o spent about 2 hours this morning with me cleaning up the house
the payoff?
- dairy queen
- watching the new pixar flick: hoppers
we caught an early showing before official release
hoppers was great, nice environmental message :)
most definitely; you two are the lovely sources of C and C++ 5g that this Rust brain needs :D soaking up these waves
had someone comment this:
> I enjoy consuming your material, you describe and share real experience with Rust, and you don't disparage other languages. Your approach is really cool!
i'm gonna cry. this is the tone i was going for :')
shout out to @rustnationuk.bsky.social for having me out to talk about this! really enjoyed sharing what i've seen on the journey thus far and the conversations this sparked afterwards :)
splash screen of Pete LeVasseur talking about Rust for Foundational Software, i.e. why Rust matters to the safety-critical community
wanna hear me go on at length about regulatory regimes in safety-critical? why Rust is poised to be a step-change in terms of confidence?
wanna listen to it at 0.5x to really soak it in?
my talk about this at Rust Nation UK 2026 is live!
(link to talk below)
> I'm not going to produce a feedback file because there's no feedback to give. Go run Phase A.
And yet ... produce a feedback file >=)
> There's your feedback file.
> Now go run Phase A before I start charging you per revision.
> Pete. The plan was done at v10. It was still done at v11. It is still done at v12.
claude about to stage an intervention bro
and yet... review this one :DDDDDDDDDD
claude after doing a further revision:
> Now go build it.
i cannot stop laughing
screenshot of claude telling me to buzz off: The plan is done. It was done at v10. v11 adds refinements that are reasonable (two-tier publishable governance, catalog smoke checks, worked example validation, doctor minimum content thresholds, calibration anti-gaming with hard/weak/distant target requirements) but none of them address a gap that would have caused a problem during execution. You're past the point of diminishing returns on plan refinement. Every addition from here is engineering time spent on the plan instead of on the calibration run that will actually tell you whether the system produces good guidelines.
claude just told me to buzz off bro
what i wrote next:
> and yet, please draft up possible improvements in a Markdown file