Estimate project
← All posts

A Rust journey: from Milan meetups to a distributed system written in Rust

Meet the next expert in our Rust interview series – an API/DevEx Software Engineer at a company building a durable-execution platform.

3 min read
Rust

In 2025, Rust turns 10 – a big milestone for the language and its lively community! In our Rust interview series, we share perspectives from prominent community leaders who are shaping the Rust ecosystem.

Meet our next expert – an API/DevEx Software Engineer at a company building a durable-execution platform.

How did you first get introduced to Rust, and what were your initial thoughts about it?

Rust started out as a hobby for me, and I would go to the Rust meetup in Milan, where people talk about their passion projects. At one point I even gave a talk about a side project of mine: building a FUSE filesystem in Rust!

Some time later, I began using Rust at work, first at a large open-source software company and then at my current company, which relies heavily on Rust.

My first, rather predictable impression: wow, that’s one steep learning curve!

Can you share a moment when you realized, “Wow, Rust is amazing”? What features or capabilities of Rust made you feel that way?

In my view, the “borrow checker” is the standout feature, once you get your head around it. Coming from GC-based languages, I learned from the borrow checker a different, more structured way of thinking about who owns a value and who may access it mutably or not. I’ve carried this knowledge over to every other language I’ve worked with since.

Something else I really like in Rust is that Futures are designed around polling. It makes reasoning about concurrency, and about who drives futures to completion, very simple, which matters a lot when you debug highly concurrent applications.

Finally, macros are fantastic – creating compile-time DSLs has never been easier!

If you could add a new feature to Rust, what would it be, and how do you think it would benefit developers?

I’d like to see better support for dynamic/virtual calls and nicer ergonomics for Futures/async Rust. Especially with the latter, I still end up far too often having to Box a future or cast the pin_project spell just to keep the compiler happy.

A few small extensions to the type system (but not too many!) would also be very welcome, such as negative/disjoint trait bounds.

What’s your favorite programming meme?

I’m not sure there’s a meme for it, but my colleagues often say: Rust, straight to the hard problems!

What tools and libraries do you rely on when working as a software developer?

For the IDE, it’s Intellij IDEA all the way, and at my company we rely on justfiles to script commands together. When it comes to libraries, I use fairly standard things across all my projects: tokio, serde, hyper, thiserror, futures, etc.

Tell us about a time when Rust made a significant difference in a real-world project.

The platform I work on is a production-grade distributed system written entirely in Rust. I’ve lost count of how many logic errors the compiler caught at compile time thanks to Rust’s type system and borrow checker!

How has the Rust community shaped your programming journey? Are there any standout interactions or stories of support you’d like to share?

The Rust Meetup in Milan was great fun. Hats off to the organizer, who encouraged us to present our hobby projects.

What advice would you give to someone just starting out with Rust?

It demands time and patience, but when you get there, you’ll have mastered a fantastic language and gained a store of knowledge that carries over to other languages as well.

How have you seen Rust evolve over the years, particularly in your area of work?

I haven’t used Rust long enough to really speak about how it has evolved, but async traits were certainly a great addition, and we’ve felt that in our codebase.

Is Rust only for systems programming, or do you see it as a valuable technology in other areas as well?

In my opinion, that depends on Rust’s future development. If Rust makes virtual calls and async/await more ergonomic, and maybe even gains a GC (while keeping the borrow checker!), it will become far more accessible to a broader audience.