"Zero To Production In Rust" is complete 🦀 . It is a start-to-finish guide for building APIs using @rustlang. A mix of pragmatic advice and foundational concepts. @zero2prod is the book I wished I had when I started. Two years in the making - it feels surreal to be *done*.

If you're in a position to hire a compiler developer, rush it!. Giving @compiler_errors the opportunity to continue working on Rust is probably the most impactful contribution that your company can make to the project.

That beautiful feeling of being ~done on a 35k lines* PR 🍉. *Don't do this at work. **Many lines are test snapshot updates.

Little typo: jobs AT mainmatter DOT com.

We have another opening at Mainmatter, this time for a *technical writer*. You'd be working directly with me on new Rust training material, blog posts and other kinds of technical long-form content. If you're interested, send your resume job AT mainmatter DOT com

An even better solution: you can set an MSRV *just for clippy* via clippy.toml. This will configure a variety of lints to behave as if you were using that version to run clippy, including the collapsible_if one. Back to fearless toolchain updates!

If you want to mitigate the problem, slap `#![allow(clippy::collapsible_if)]` on your crate.

Rust 1.89.0 will stabilize let-chains (yay 🎉). In the same release, clippy will flag `if` statements that can be collapsed further using a let-chain. Outcome: your CI will fail when 1.89.0 is released, and you can't fix it ahead of time because the feature clippy wants you to.

It's official now: I'll be a speaker at RustConf 2025 🎉. My talk falls into the "Interop & Migration" theme, covering the work we've been doing with Redis, supporting the migration of some of their C code to Rust. You'll get all the details when the full schedule is announced!

Two things can be true at the same time:.- You can achieve ~everything with enough practice.- Dan Luu is spot on when he says that "95%-ile isn't that good". If you've never read the article, this is your chance:

A bunch of Italian friends talking shop about Rust 😄.

If you're not at PyCon, you can find the workshop material online: It's exercise-based, like most of our trainings here at Mainmatter.

The Rust-Python workshop at @pyconit is about to start!. Seek me out if you're at the conference and you want to talk about native extensions!

You can submit your proposals at

Two weeks left to submit your talk proposals for EuroRust 2025 ⏳.The CfP closes on June 2nd!. We're looking for a wide range of contributions: beginner-friendly talks, reports on Rust industrial usage, deep-dives on language features or crates, tutorials, etc.

Pavex is now officially registered as a trademark!. Another to-do item can be crossed off the public beta checklist ✅

Spoiler alert: all lines trending in the Rust direction!.

The Rust team at Mainmatter has grown, but we need to grow it further!. We're looking for freelancers to help us migrate a database from C to Rust. It's an incremental rewrite: a module at a time, interfacing with the existing C code. European hours, full remote, 4 days a week.

The goal is for the API to be ~stable on release. The feedback I received (and keep receiving) during the beta is making that more and more of a possibility as we converge on a defensible design.

In case you were wondering: work on Pavex continues!. I'm reworking the public API to minimize friction. We're shifting towards attribute macros for component egistration. This removes the need to spell out raw paths, a major pain point of the first beta version.

Useful heuristics: if a new feature allows you to delete entire sections out of your documentation, it's a good change.