In Minecraft, every world is built from blocks. At the very bottom lies bedrock: an unbreakable foundation that everything else rests on. Above it sit layers of stone, dirt, sand, and other materials. The surface looks quite beautiful, but the resources essential for survival are buried deep below, and players must descend to reach them. Of course, they’re warned: “don’t dig straight down”: remove the block under your feet and you might plunge into lava.

Our technological infrastructure works the same way. We often focus on the surface: APIs, clusters, and users. But just above the bedrock of our systems are the crucial yet less visible layers: hardware drivers, kernels, bootloaders. Developers know that digging too far down can be difficult and risky because of the complexity involved. Yet, as in Minecraft, you can descend safely with the right approach, working your way towards a once untouchable foundation to solve the biggest challenges you face such as security, performance, or velocity.

This talk traces through the way we think about layers of software today and how simplifying those layers can lead to improvement in outcomes in both functionality and security. It also will explain a strategy for working on layers that a developer doesn't traditionally work on.

This isn't about software being a silver bullet or any single technology solving our problems. It’s a mindset to restore holistic system security, not accepting the status quo just because it’s always been that way. Stripping back layers of complexity and building what we really need, all at the bottom layer of the stack.

Security done right isn't a gate that slows people down, it’s an enabler. But getting there requires us to stop accepting that some layers are just "too hard" to fix and start building the bedrock our systems deserve. You can't solve security at just one layer. You have to do it all, from bedrock up.