Warp Terminal; De Toekomst van de Command Line

Warp Terminal is niet zomaar een terminal, het is een volledig heruitgevonden tool die jouw dagelijkse ontwikkelwerk sneller, slimmer en intuïtiever maakt. Features à la 2025, niet à la 1975 😉. Gebouwd in Rust voor maximale snelheid en veiligheid, speciaal voor developers die vinden dat de CLI eindelijk mee mag evolueren.

Wat maakt Warp zo bijzonder?
Command Blocks – Elke opdracht krijgt z’n eigen input/output-blok: overzichtelijk en je kunt er makkelijk doorheen navigeren en (gedeeltes) kopiëren;
Input Editor – Multi-line editing, syntax highlighting alsof je in VSCode zit. En ook inline documentatie bij flags;
Ingebouwde AI – Realtime hulp bij errors of complexe commando’s. Inclusief Agentic Mode (natuurlijke taal → werkend commando), ondersteuning voor GPT-4o, Claude 4, en zelfs voice input;
Warp Drive – Deelbare command histories en workflows: perfect voor teams.

Warp maakt van de terminal niet zomaar een betere tool, het word je centrale productiviteitshub. Inmiddels is deze Terminal niet meer alleen voor MacOS maar ook uitgebracht voor Linux en Windows, waardoor de presentatie voor iedereen interessant is.

Building Intelligent Apps with Azure AI and .NET 9

In this talk we learn what the current Azure AI landscape looks like, what has been added recently, and we start building a .NET 9 Blazor app that integrates with an Azure AI Foundry LLM.

Terminal Productivity: Unlocking the Full Power of Linux

In this workshop, we'll explore a range of techniques to boost your efficiency on Linux by harnessing the power of the terminal. We'll cover keyboard shortcuts, lesser-known commands, and effective ways to chain multiple operations for maximum productivity.

Contemplating Reliability - Why less can be more

Intuitively, we want to create good applications whose reliability is pushed to the maximum. What we tend to overlook is the hidden drawbacks of aiming for an overly high reliability, like mental stress during an outage and hesitance towards rapid feature development. Accepting that failures may occur takes off stress from DevOps teams and allows them to focus on what really matters for the end-users. In this talk, we’ll discuss an outline for a framework on how much failure DevOps teams should reasonably expect using error budgets. While technical errors may abound, user impact may be negligible, so keeping an eye on end-user impact is of the essence. This will show us how severe an incident really is and help us stay sane during “unimportant” incidents. Moreover, when reliability is surpassing expectations, we will learn that we can allow for more “risky business” and innovate fastly, improving on customer experience in another way.

Introduction to Chaos Engineering

Chaos engineering is a relatively new discipline within software development, mostly aimed at (but not limited to) distributed systems. While often misinterpreted as ‘breaking stuff in production’ (which sounds cool, but doesn’t add much value), I will show that this discipline should be understood differently. It enables developers to make the inherent complexities (‘chaos’) in modern applications insightful, and lets us detect vulnerabilities and unexpected dependencies in the system in a controlled way.

I’ll show how a chaos engineering tool like Gremlin can help us to conduct experiments (e.g. by tweaking latency parameters or time-travelling to Daylight Saving Time). Besides detecting potential problems in our systems (and diminishing the blast radius of those failures), these experiments also provide a perfect opportunity to test and improve our alerts.

DevOps / Software engineers interested in improving system resilience and pro-active spotting bugs and unexpected dependencies.

Goodbye Swashbuckle: Exploring Native .NET OpenAPI

If you've been using Swashbuckle and Swagger UI with ASP.NET APIs, you may have noticed a change starting in .NET 9: the tooling you have relied on for years has disappeared... When I first ran into this, it felt unsettling. Until it made sense. Microsoft introduced first-party OpenAPI support with Microsoft.AspNetCore.OpenApi, reducing dependencies and making API documentation much simpler. Swashbucklecan still be included as NuGet, but I'll try to convince you why you might want to make the switch.

I'll walk through what these changes mean in practice: the shift from Swashbuckle filters to document, operation, and schema transformers, Among other things, we will separate public from private APIs in different openapi files, wire up OAuth authentication, configuring API versioning. I'll highlight my favorite .NET 10 additions, including OpenAPI spec generation at build time, OpenAPI 3.1 support (with a caveat on when *not* to use it), multiple output formats. We finish by exploring the Scalar testing UI, which stays responsive with large payloads and does not make you want to reach for Postman.

Through a series of live demos, you'll see how I migrated a production API project away from Swashbuckle, tackled the gotchas that nobody warns you about, and ended up with an API setup with less ceremony, cleaner docs, and one fewer dependency.

Whether you are maintaining an existing Swashbuckle setup or starting fresh, you will leave with a clear migration path and a set of patterns ready to apply the next morning!