This technical talk examines the most prevalent pain points facing Rust web developers today and explores how the community is addressing them.


The Rust web ecosystem has made incredible progress, but let's talk about what we don't discuss enough: the rough edges. Every web developer working in Rust has battled macro-heavy frameworks that obscure what's actually happening, ORM integration headaches that turn simple queries into type gymnastics, and error handling that makes it hard to return clean, user-friendly error messages instead of exposing internal implementation details.
This technical talk examines the most prevalent pain points facing Rust web developers today and explores how the community is addressing them. We'll discuss common developer frustrations, emerging patterns and solutions, and honest assessments of what's improving versus what remains challenging. Whether you're shipping production Rust backends or evaluating the ecosystem, you'll walk away with a clearer picture of the real-world challenges and where the community is headed.
I’ll share what the Rust job market really looks like in 2025 — where companies are hiring, which skills stand out, and how the recruitment process actually works behind the scenes.
In this talk, we’ll re-create the core ideas of Karpathy’s micrograd, but entirely in Rust.
In this talk, we'll explore the current state of AI development in Rust, highlighting key crates, frameworks, and tools. Covering the essentials from ML and NLP to integrating LLMs and agent-based automation.
We’ll take a deep dive into Rust channels — from synchronous channels to asynchronous channels — to explore how message passing enables reliable concurrent programming.
In 2024, I added the `Option::as_slice` and `Option::as_mut_slice` methods to libcore. This talk is about what motivated the addition, and looks into the no less than 4 different implementations that made up the methods. It also shows that even without a deep understanding of all compiler internals, it is possible to add changes both to the compiler and standard library.