New to testing in C#? Start here 👇 xUnit.net course → from your first test to pro practices. 🔗 dometrain.com/course/from-ze…

Next time you start a new project or refactor an existing one, check your tests, global usings can save you hours of repetitive work.

The result? Your test files are cleaner, easier to read, and you reduce the risk of typos or missing references. All in minutes, zero risk. ✅

Most IDEs can even automate this for you: highlight a 'using' → convert to global using. ⚡

With global usings, you declare those common namespaces ONCE, and they're available in all files. No more clutter at the top of every file.

Typically, test files repeat references to your domain, core, or testing frameworks (`Xunit`, `Moq`, etc.). It's tedious and adds boilerplate.

Ever get annoyed by repeating the same 'using' statements in all your test files? 🧪 C# 10+ has a neat fix: global usings. Let's see how it simplifies your test projects. 👇

Still on xUnit v2? You're missing out. ⚡ xUnit v3 supports TestContext.Current.CancellationToken and assembly-level logging attributes. Upgrade in minutes, reduce boilerplate, get clearer integration test results.

Lesson? Don't let your developer's tunnel vision push you towards complex solutions. Step outside your comfort zone → sometimes the most straightforward fix is the best.

Switching formats cut my payload by 40%. No infra changes. No new tools. No complexity.

👉 Enter WebP & AVIF - WebP: ~30% smaller than JPEG - AVIF: up to 50% smaller (with no visible quality loss)

I was still serving JPEGs and PNGs like it was 2015. Even compressed, they’re no longer optimal.

When I rebuilt my site, Lighthouse flagged performance issues. My instinct? "I need a CDN or smarter caching." But the root cause wasn't infra. It was… images.

As .NET devs, we often reach for infra tools first: - caching, CDNs, scaling servers. But sometimes the biggest performance wins don't require any of that. 👇

Video here → piped.video/LC1nukDZNN8?si=qT3e…

🎥 If Your Integration Tests Feel Impossible to Debug, Watch This! Ever tried debugging an integration test, only to get nothing in your output window? No logs, no console messages, just confusion. That's exactly what xUnit v3 fixes with CaptureOutput. Now, you can finally see the logs from your tests, without messy workarounds or console hacks. This isn't just about cleaner logs, it's about understanding what's really happening inside your tests, faster. If you've ever spent more time guessing than debugging, this one's for you. 👀 Watch the full video on YouTube 👇

Most devs see a perf issue and jump straight to infra fixes: caching, servers, etc. But sometimes the biggest wins come from the simplest change. My site's payload dropped 40% — not by scaling infra, but by switching image formats.

Imagine if we made it simple! Today started off with words of wisdom from keynote speaker @gsferreira #NDCPorto piped.video/3brPDRvbIP8

Some days, goals become reality. Today was one of those days. @NDC_Conferences Porto keynote ✅

A very important message from @gsferreira at @NDC_Conferences Porto: do more with less 👌

It’s that time of year again #ndcporto