LOADING
This talk explores what it means to write scientific software that lives up to the standards we expect of science itself.
Good science demands transparency, reproducibility, and rigour. The software underpinning it should be no different. In labs, hospitals, and research institutes, Rust is beginning to appear where it matters most: places where correctness and clarity aren't just nice-to-haves, but the foundations of trustworthy research.
This talk explores what it means to write scientific software that lives up to the standards we expect of science itself. We'll look at how Rust's emphasis on explicitness and safety aligns naturally with the principles of open, reproducible research, and how we can go further by treating tests as proof, documentation as methodology, and readable code as a form of scientific communication.
Drawing on examples from epidemiology, synthetic data, and biomedical infrastructure, we'll examine how to build tools that are auditable, maintainable, and built to last. We'll also reflect on how the choices we make today, in our dependencies, our environments, and our defaults, shape whether the next generation of researchers can understand, verify, and build on our work.
This technical talk examines the most prevalent pain points facing Rust web developers today and explores how the community is addressing them.
The talk explores how Rust’s type system and memory safety can be leveraged to enforce mandatory guardrails at the infrastructure level, where traditional frameworks often fall short.
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.
This session we will delve into the sometimes murky world of procedural macros - showing some of the great tooling available for understanding the code generated, such as cargo expand, and the key building blocks we will need for writing our own.
In this talk, we’ll re-create the core ideas of Karpathy’s micrograd, but entirely in Rust.
This talk puts popular Rust rewrites to the test. We'll examine how these tools stack up against their battle-tested predecessors, looking at real-world performance, compilation times, binary sizes, feature completeness, and ecosystem maturity.
