Publishing NuGet packages has traditionally required one uncomfortable compromise: a long-lived API key had to exist somewhere in the delivery pipeline. Even when that secret was stored in a secure CI system, the model still relied on a credential that could be leaked, copied, mis-scoped or forgotten. Once exposed, that key could often be reused until someone noticed the incident and rotated it.
Read Blog Post
After many years of workarounds, design discussions and library-level substitutes, unions are finally becoming a first-class part of C#. The proposal in the C# language repository is no longer a distant idea. With the feature now appearing in the .NET 11 preview train as an early C# 15 capability, the direction is concrete enough to discuss in practical terms.
Read Blog Post
C# is a powerful language, but there is one road it has not yet fully paved: native discriminated union types. Developers have been working around this absence for years, typically choosing between throwing exceptions for non-exceptional paths, returning nullable values, using out parameters or layering custom wrapper classes on top of every service boundary. Each of these approaches carries a cost - in clarity, type safety or runtime efficiency.
When building cloud-native .NET applications, two goals often matter at the same time: a fast local development loop and a clean path to real Azure resources for publish mode. .NET Aspire with Azure Cosmos DB supports exactly this pattern.
Read Blog Post
The .NET team just released the first preview of .NET 11 and there is already a lot to talk about. While this is an early preview - not a release candidate - the breadth of changes touching the runtime, libraries, ASP.NET Core, Blazor, C#, the SDK and Entity Framework Core gives a clear picture of where the platform is heading. Let me walk you through the most important changes you should know about.
Read Blog Post
Large language model agents can appear intelligent while still producing unstable output across runs, contexts and tasks. In practice, this instability is rarely caused by model quality alone. The dominant factor is often missing operational structure: no explicit boundaries, no role-specific constraints, no reusable task patterns and no agreed execution policy.
Read Blog Post
Local SQL Server database files provide a pragmatic way to keep a real SQL Server engine close to the application without provisioning a full server. A LocalDB database lives in a single .mdf file (plus a log file), runs in user mode and behaves like SQL Server for most application scenarios. That makes it a strong fit for local development, integration tests and tooling that needs relational features without the overhead of infrastructure setup.
Read Blog Post
The landscape of AI development is shifting rapidly from simple chat interfaces to fully integrated, agentic workflows like the Ralph Loop . GitHub has recently introduced the GitHub Copilot SDK , a powerful toolkit that allows developers to programmatically harness the engine behind the GitHub Copilot CLI.
Read Blog Post
What if an AI agent could write code, run tests, fix errors and repeat this process autonomously until the job is done? The Ralph Wiggum Method makes this possible with a simple but powerful loop pattern. Named after the lovable Simpsons character, it embodies the philosophy: persistence wins over perfection.
Read Blog Post
Single Page Applications like React expect the server to always return index.html and let the client-side router take over. On Cloudflare Workers you can do that without custom code as long as wrangler.toml is set up correctly. This post shows the minimal configuration and why two options are essential for SPAs.
When working with Pull Requests (PRs) in GitHub, it is often helpful to provide immediate feedback or relevant information directly in the conversation view. Whether it is a deployment preview URL, code coverage results or a summary of changes, having this information automatically posted as a comment saves time and improves collaboration.
Read Blog Post
Feature management is a key technique in modern web applications, allowing you to enable or disable features dynamically without redeploying your code. In ASP.NET Core, the Microsoft.FeatureManagement library provides a robust way to implement feature flags. But what if you want to ensure that administrators can always access certain features, even if those features are disabled for regular users?
Read Blog Post
Die deutsche Version findest du hier: Home Assistant via Docker auf einer Synology NAS installieren
Home Assistant is the “hub” for many smart homes: local-first, extensible and backed by a huge ecosystem. If you already run a Synology NAS, it’s often a great platform to host Home Assistant in a container-no extra Raspberry Pi required.
Read Blog Post
You can find the English version of this guide here: Install Home Assistant on Synology NAS with Docker
Home Assistant ist für viele der “Hub” im Smart Home: lokal, erweiterbar, mit riesigem Ökosystem. Wenn du bereits eine Synology NAS hast, ist sie oft die perfekte Plattform, um Home Assistant als Container zu betreiben – ohne extra Raspberry Pi.
Read Blog Post
If you build systems that pass structured data through large language models (LLMs), you eventually hit the same set of issues:
Read Blog Post
IMemoryCache is great for speeding up expensive operations (database reads, HTTP calls, heavy computations). But many real systems need more than a TTL:
Feature flags are a great way to ship safely, run experiments and keep production changes reversible. In .NET, the de-facto standard is Microsoft.FeatureManagement .
Read Blog Post
.NET 10 is the next Long-Term Support (LTS) release in the .NET family. LTS matters because it’s the version many teams standardize on for the next 2-3 years: you get a stable baseline, predictable support windows and a natural time to pay down technical debt (tooling, CI images, container base images, dependency bumps).
Read Blog Post
You can find the English version of this guide here: Self-Hosting Vaultwarden (Bitwarden) on Synology NAS with Docker
Passwort-Manager-Dienste sind in den letzten Jahren deutlich teurer geworden. Gleichzeitig ist mein Vertrauen in kommerzielle Anbieter - insbesondere aus den USA - gesunken. Als jemand, der Wert auf digitale Souveränität legt, war es für mich an der Zeit, die Kontrolle über meine Passwörter zurückzugewinnen. Ein Jahr habe ich Proton Pass ausprobiert - aber ich bin nicht wirklich zufrieden: die Features in der App sind eingeschränkt, und die Synchronisation mit Browsern funktioniert nicht immer. Die Browserintegration und die Erkennung von Passwortfeldern scheint noch in den Kinderschuhen zu stecken.
Read Blog Post
You can find the German version of this guide here: Vaultwarden auf Synology mit Docker selbst hosten
Password manager services have become significantly more expensive in recent years. At the same time, my trust in commercial providers - especially from the USA - has decreased. As someone who values digital sovereignty, it was time for me to regain control over my passwords. I tried Proton Pass for a year - but I’m not really satisfied: the features in the app are limited and synchronization with browsers doesn’t always work. The browser integration and password field recognition still seem to be in their infancy.
Read Blog Post