I contributed LTO-related changes to many open-source projects, and had a lot of interesting discussions with their maintainers about LTO. In this talk, I want to share with you my experience.

Link-Time Optimization (LTO) is a compiler optimization technique that helps a lot with optimizing software beyond the default Release profile. This optimization can be enabled by a single line in your Cargo.toml file. But is it so easy in the real world?
I contributed LTO-related changes to many open-source projects, and had a lot of interesting discussions with their maintainers about LTO. In this talk, I want to share with you my experience. We will discuss the following topics:
* What is LTO? Why is it useful?
* What kinds of LTO do we have in Rust? With their pros and cons in different scenarios.
* LTO adoption state in the Rust ecosystem and what we can do with that.
* Common and not-so-common LTO issues and how to mitigate them.
* How to integrate LTO into your project properly.
* And of course answer all your questions about LTO!
After the talk, you will be much more prepared to optimize your Rust applications with LTO and avoid as much LTO traps as possible!
In this talk, we’ll re-create the core ideas of Karpathy’s micrograd, but entirely in Rust.
This talk explains how Rust debugging actually works: how compiler-generated debuginfo (DWARF/PDB) maps binaries back to source, and how LLDB/GDB interpret that data in practice.
In this talk, we’ll explore battle-tested best practices for integrating Claude Code into a professional Axum development workflow without compromising on Rust’s core values: correctness, clarity, and maintainability.
I'll initiate you in the art of 'CAN bus sniffing': Connecting to the central nervous system of a modern car, interpreting the data, and seeing what we can build as enthousiastic amateurs.
For infrastructure engineers, SREs, platform teams, and Rust developers who've felt the pain of configuration drift, failed deployments, and infrastructure code that simply doesn't scale safely.