New blog post!
https://corrode.dev/blog/bugs-rust-wont-catch/
In which I talk about non-obvious bugs Rust won’t prevent.
Kinda went a bit viral already. It’s on HN and Reddit right now in case your looking for additional discussion.
Remote
Matthias Endler
@mre@mastodon.social
mastodon 4.8.0-nightly.2026-10-06I mostly talk about 🦀 Rust and 🧑💻 Open Source. Host of 'Rust in Production'.
Reach out for Rust contract work / consulting!
Some of my other projects:
https://search.corrode.dev
https://tools.corrode.dev
https://analysis-tools.dev
https://openpodcast.app
https://lychee.cli.rs
1449 Followers
470 Following
38 Posts
Joined May 11, 2017
Consulting:
Personal Blog:
Code:
Rust Search Engine:
Hey if anyone finds the time, I’d be thankful for any feedback on this new blog post.
It’s about making Rust programs more robust for real world scenarios.
https://corrode.dev/blog/hardening-rust/
I hope it’s okay that the post is quite long. There is a table of contents in case you’d like to scan the post first.
What I’m looking for:
- Is this type of content helpful?
- Anything else I forgot or should link to?
- Any related topics you’d like to read about?
Thanks!
Here's the post I wish I had when I first started programming.
If you know someone just beginning to code (especially students), maybe pass this along?
Would've saved me a lot of head-scratching and "why didn't anyone tell me this earlier?" moments.
We'll be back for season 6 of Rust in Production tomorrow! Have an amazing roster lined up.
In the latest episode of Rust in Production, we talk to members of the Rust Foundation leadership and board about what the Foundation does, how it relates to the Rust Project, and why that distinction matters for teams using Rust professionally.
We cover a lot of ground, including infrastructure, security, interop, maintainer support, governance, corporate membership, and open-source funding.
Episode: https://corrode.dev/podcast/s06e08-rust-foundation?cache=1
#rustlang #rust
Season 6 of Rust in Production is finally here!
The first episode features Cloudsmith who *didn't* rewrite their Django monolith in Rust. They just fixed the slow part with Rust extensions and services. The result was a massive speedup, minimal disruption.
Not every Rust adoption has to be "loud." Sometimes the quiet wins are the best ones. :)
Episode page: https://corrode.dev/podcast/s06e01-cloudsmith/
Super happy to be a part of RustWeek again. Thanks! 😊
Rust migration at Clickhouse.
„C++ is a pain. We still have segfaults in production.“
FOSDEM, Rust dev room
Link to livestream:
https://live.fosdem.org/watch/ub2252a
This is super exciting and I’m looking forward to that session! DM me if you have any questions you always wanted to ask the Rust4Linux team.
Whoever implemented the feature in Zed where joining two comment lines with Vim shortcuts automatically strips redundant comment markers: thank you. 🫶
@woolf@mastodon.social restoring our prod db. 🙃
Rust migration at Clickhouse.
„C++ is a pain. We still have segfaults in production.“
FOSDEM, Rust dev room
Link to livestream:
https://live.fosdem.org/watch/ub2252a
Replying to
Thanks to @jonhoo@fosstodon.org for taking the time to do the interview and to the entire team at Helsing.
Replying to
@jnsgruk thanks! And I highly appreciate that the audit results were made public. This way, we can all learn from them.
I’m optimistic about the future of uutils and believe it was the right call to integrate it.
Excited to see what will be next for Ubuntu+Rust :)
Replying to
@mnf@mastodon.social oh, that's a good one! Fun story from University: the task was to build a list datastructure in C++ that could be converted into builtin datastructures like vectors. Took me two weeks and the other students two days. Turns out I misread the assignment and implemented an STL-compatible container, which is a whole different ballgame. Instructur was flabbergasted when they looked at the result. Learned so much about C++ internals that it was totally worth it. (Forgot all of it, of course.)
Replying to
@calisti true. The network was down for a few moments and I wasn’t sure if the post worked. Too late now. 😅
Replying to
@StrangeNoises@mastodon.social oh, that's great to hear. I'm of the opinion that culture is more important than skill. You can always learn what you don't know, but fixing engineering culture is super hard. I like to work in teams where continuous learning is a normal part of day-to-day work and where people are naturally curious.
When they asked the question, they tested culture fit. :)
Replying to
@helmutstrasser@mstdn.social well, brilliant is a strong word, but I'm glad you liked it. Gives me the courage to write more and follow my gut feeling about the choice of topics.
Replying to
@mahryekuh@fosstodon.org thanks! Much appreciated. I'll make sure to keep the post up for your return. ;)
Replying to
@b_n@techhub.social you know what I like the most about this photo? It has some nice dynamic to it. You can "feel" that Niko explains something, and I really like the framing of the photo. So, thanks again.
Replying to
@TimWardCam@c.im oh yes, I can relate to that. I understand that it's not always possible to spend that amount of time on reading the reference before getting started. However, I feel like its a muscle one can train. Narrowing down to the section, which likely contains the relevant information can be practiced and many search engines can deep-link into references surprisingly well. So I'd search for "Python datetime reference" or "nginx site configuration reference" and take it from there.
Replying to
@artfulrobot@fosstodon.org same. I know less than I did when I graduated University because it turns out nothing is simple. So nowadays I consider myself a beginner in most computer things again. It definitely helps to have a "learner" mindset. 😅
Replying to
@sanityinc@hachyderm.io
It's fixed thanks to Elias Prescott. 🚀
https://github.com/mre/endler.dev/pull/66
Replying to
@sanityinc@hachyderm.io oh! Thanks for the comment. I broke the mobile view with some recent CSS changes apparently. Thought I tested that, but no dice. 😅 I'll look into it when I get a chance.
Replying to
@loke@functional.cafe @mnf@mastodon.social yeah, maybe, but mostly for compatibility reasons. An STL container needs to follow quite a few conventions.
https://en.cppreference.com/w/cpp/named_req/Container
Here is the vector implementation:
https://github.com/gcc-mirror/gcc/blob/master/libstdc++-v3/include/bits/stl_vector.h
Mine wasn't nearly as complicated, but it had the most important parts
It's always fun to work on that low level. I constantly think "wow, I can understand this!?" 😅
Replying to
@mirabilos@toot.mirbsd.org true. As you said, you need to know enough about it to steer clear of it, which probably means you touched it before. 🙃 But yeah, you don't have to be the go-to person forever. Documentation, automation, delegation, etc. are my preferred ways out. (Still not good at that, though.)
Replying to
@jacobmealey@mastodon.social we haven't met, but just from this interaction alone I know that you're on the right track. Thanks for the feedback. :)
Replying to
@thom@fosstodon.org well thanks. What works for me is sitting down and writing these pieces in one go without much editing. It works because it's simple and comes from the heart. Glad you enjoyed it. :)
Replying to
@jdrouet@mamot.fr Helsing is a defense company, yes. The conversation is mostly about the engineering challenges and design patterns for writing robust Rust code, though.
Replying to
@TimWardCam@c.im I think the key is to ask: "call on what"? Then I would search through the reference of $what to see what I can call on it and learn the name of the thing I'm looking for. Sounds easy enough? 🤔
Replying to
@TimWardCam@c.im not saying this is not an effective strategy, but I gave up on Stack Overflow a while ago. The good answers are rarely at the top nowadays. Takes some experience to know what to look for. Instead, I read through the entire documentation of the main tools (languages, frameworks) I use. It takes a surprisingly short amount of time and I don't have to do it in one sitting. Couple hours of time well invested after which I feel much more confident and don't have to rely on a thrid party.