I’m excited to announce that the dotNetDave No Rest for the Wicked World Tour is rolling into Warsaw, Poland, for .NET Developer Days 2026 Warsaw, on October 20th – 21st, 2026.

I’m thrilled to be speaking at this event for the first time, and it’s my first time to Poland!

Make sure to arrive early and grab a seat up front — you just might catch a custom dotNetDave guitar pick flying through the air and other swag! These sessions are going to be packed with energy, insights, and a whole lot of fun.

Below is the info for the sessions I’ll be presenting — I’d love to see you there! It’s going to be a blast, and I promise you’ll walk away with something useful (and maybe even a laugh or two). Don’t miss it!

Röck Yoür Cöde: Stop Guessing — Benchmark Like a Pro

You think your code is fast? Prove it.

Modern .NET developers have more tools than ever—but too many are still guessing when it comes to performance. The result? Slower applications, higher cloud costs, and problems that don’t show up until production.

And here’s the kicker: even AI tools like GitHub Copilot can generate code that compiles, works… and performs terribly. If you’re not measuring it, you’re trusting it—and that’s a risk.

In this session, veteran engineer and author David McCarter (dotNetDave) shows how to cut through the noise and make performance a data-driven discipline. Using BenchmarkDotNet and the DotNetTips.Spargine.Benchmarking library, you’ll learn how to measure execution time, memory allocation, and scalability the right way.

Through live demos and real-world examples, you’ll see just how wrong “common knowledge” about .NET performance can be. You’ll learn how to build benchmarks you can trust, avoid traps like JIT optimizations and setup bias, and turn raw numbers into decisions that matter.

Stop guessing. Stop trusting assumptions.

Measure it. Prove it. Ship code that performs.

Attendees will learn:

• How to build accurate, repeatable benchmarks using BenchmarkDotNet
• How to eliminate measurement noise and avoid misleading results
• How to compare multiple implementations and identify the fastest approach
• How to measure memory allocation and understand its impact on performance
• How to apply benchmarking in real-world, cloud-based scenarios
• How to integrate benchmarking into the development lifecycle before release

Software Engineering Goes to 11: The Rock ’n’ Roll Commandments for Code That Rocks

Great software has a lot in common with great rock ’n’ roll. You don’t walk on stage without rehearsing, you don’t record an album without structure, and you definitely don’t tell everyone it rocks until you’ve actually heard it.

Software engineering should work the same way.

In this high-energy session, we’ll crank software development up to 11 with a set of rock-inspired commandments covering architecture, unit testing, naming, refactoring, error handling, benchmarking, simplicity, documentation, code review, security, and AI-generated code.

Along the way, we’ll look at why developers still fall into the same traps despite decades of better languages, frameworks, tools, and automation—and why engineering judgment matters more than ever.

And because 10 just isn’t loud enough, the final commandment tackles one of today’s biggest risks: letting AI generate production code without strict validation from an experienced software engineer.

Expect practical engineering advice, real-world lessons, a little humor, and plenty of rock ’n’ roll.

Code. Design. Test. Measure. Refactor. Rock.

Resources

• TBA