#csharp

Bug fixing is often treated as the process of locating and correcting defective code. In complex...

Over a two-and-a-half-year engagement I migrated 42 financial workflows from a legacy Visual FoxPro...

Before designing anything, find where the current platform is starting to limit the business, and...

Disclosure: I work on SelectPdf, the library used in this article. It's a commercial library with a...

Your character can move. Great! But what happens when it reaches a wall? What about gravity, slopes,...

Using AI Only Where It Adds Value in Code Automation When we talk about AI-assisted...

Last weekend I built tilt-check for my partner, who trades micro futures at night from Korea. Before...

A recurring inventory-sync job ran fine in testing but froze in production when multiple instances hit the same EF Core transaction. Tracing the deadlock revealed that two separate background services were updating overlapping rows without consistent lock ordering — classic deadlock territory. The fix wasn't fancy retry logic but passing a shared CancellationToken that let the second job abort cleanly instead of waiting on a lock, combined with idempotent upserts so aborted jobs could safely resume. The lesson: background jobs aren't fire-and-forget; they need cooperative cancellation, deterministic ordering, and idempotency to survive real concurrency.

My partner trades micro futures on a prop-firm account that bans fully automated trading. I wanted a...

You've finished your .NET application, run it through an obfuscator, and everything looks great. Then...

If your ASP.NET Core app needs to produce invoices, contracts or transactional emails, you usually...

Ever wondered why binding to immutable records becomes such a pain in Blazor? Because binding...