Is your codebase fragile, where one small change risks breaking something unexpected? That fragility often comes from layered or “lasagna” architectures that scatter logic across controllers, services, repositories, and models. Touching one feature means touching several layers, and every change feels slow and risky. Vertical Slice Architecture takes a different approach.
Instead of organizing by technical layer, it organizes by feature. Each slice contains everything it needs, from input to persistence, and stands largely on its own. This makes features easier to find, easier to understand, and easier to change without worrying about unintended ripple effects. It also gives you the freedom to pick the right implementation for each case, whether that means EF Core, Dapper, or raw SQL.
In this talk, we will explore how to shift from rigid layered designs to feature-oriented slices, and how that shift creates codebases that grow more naturally and stay easier to maintain. Through practical .NET examples, you will see how vertical slicing encourages clarity, flexibility, and confidence when building or refactoring applications. Layers might be fine for lasagna, but your architecture deserves something better.
Ever wonder how NASA writes software that literally can’t afford to fail? Meanwhile, back on Earth, our code is held together with duct tape and //TODO comments. The stakes might be a little lower for most of us—nobody’s oxygen supply depends on our latest API deployment (hopefully)—but reliability, maintainability, and simplicity still matter.
Enter NASA’s Power of Ten rules: a set of software engineering principles designed to minimize complexity and maximize reliability. In this talk, we’ll explore these ten commandments of mission-critical coding, from banning recursion (gasp!) to keeping functions tiny and predictable. Along the way, we’ll discuss how these rules apply beyond space exploration—to web apps, enterprise systems, and anywhere else software keeps the lights on.
Whether you’re launching rockets or just trying to keep production from crashing at 2 AM, these lessons can help you write code that’s more robust, maintainable, and maybe even astronaut-approved. So strap in, and join us for a journey through the Power of Ten—no space suit required!