In today’s world, we have advanced tools for testing and deploying apps, but internal engineering documentation is stuck in outdated practices like copy-pasting from wikis. Runme (runme.dev) rethinks documentation by turning Markdown into interactive Notebooks, using DevContainers for reliable dependencies, typed .ENV files for managing config/secrets, and cloud-native integrations. In just minutes, engineers can create interactive, testable docs that streamline processes and improve efficiency across teams.

Weeks to months after a routine upgrade from systemd 247 to systemd 248, engineers at Meta discovered a very gradual growth of memory usage in systemd-journald, from 20 MB to over 300 MB and growing. It's not a memory leak! What could it be? Come hear about how we detected it, how we tracked down the cause, what the root cause was, and how it was fixed.

systemd (with lowercase S and D) remains up until this day, both one of the most critical pieces of a system, and the least understood one. This talk explains how you can harness the power of systemd to solve common problems, including some that you didn't even know you had. What problems do you ask?, you’ll have to come and see.

The modern web stack is made up of a dozen different systems, but too few people know how to create and support them. I believe this is because systems programming has historically had too many barriers to entry, such as memory safety and the trading of expressiveness for performance. Let us explore some of the ways Rust breaks down these barriers and can make systems programming feel much more approachable to web developers.