Published:
This post covers the logging and diagnostics features you should understand before running a .NET application in any real environment. The short version is: use ILogger everywhere, log structured data instead of string-concatenated messages, and configure log levels deliberately so production logs remain useful instead of noisy.
Published:
This post covers how configuration works in modern .NET applications and how to keep secrets out of source control. The core idea is simple: settings should come from configuration providers, secrets should be stored outside your repo, and your code should read configuration through strongly typed options whenever possible.
Published:
This post covers the C# features every .NET developer uses daily. You do not need to master every corner of the language on day one, but you do need a solid grip on how types behave, how LINQ transforms data, and how async/await keeps your application responsive. These three areas show up in almost every code review, bug report, and production service.
Published:
This post covers how a typical .NET codebase is organized. New developers often focus on Program.cs and controllers, but production projects are shaped just as much by how solutions are split, how project files are configured, how packages are restored, and where compiled artifacts are written. If you understand those four pieces, you can navigate almost any .NET repository with less guesswork.
Published:
Setting Up Your .NET 8 Development Environment
Published:
This post covers the fundamentals of building a Web API with .NET 8 (ASP.NET Core). If you’re new to the ecosystem, your goal isn’t to memorize every feature—it’s to understand the core mechanics: how requests flow through your app, how endpoints are defined, how data is validated, and how responses are shaped. Once these pieces click, everything else becomes “just configuration”.