Saving a payment and then publishing "PaymentSucceeded" is two writes to two systems. One of them will eventually fail. The outbox pattern turns it into one write, with runnable EF Core code.
Let code do the counting and Claude do the reading. A weekly routine that compares Search Console periods page by page, separates demand drops from ranking drops, and turns the result into a short list of actions.
A decimal doesn't know its currency, its precision or how to split itself. A small Money type does, and it turns a whole class of silent bugs into loud ones. Runnable C# 14 and EF Core code.
A balance column tells you a number. A ledger tells you why. How to make recorded transactions the single source of truth for a wallet, with runnable EF Core code.
An idempotency key turns "the client retried" from a duplicate payment into a harmless replay. Here is a small, runnable ASP.NET Core implementation and the trade-offs behind it.
Use EF Core where you change data and Dapper where you read it for a screen or a report. Here is why the split works, with runnable code that shares one connection.
Vibe coding means describing what you want and letting an AI write the code. It works best when someone still owns the architecture, the tests and the deploy. Where it shines, where it breaks, and the guardrails that make it safe.
Two withdrawals read the same balance and both succeed: that's a race condition. Three ways to stop it in EF Core (rowversion, an atomic update, and a row lock) and when to use each.
Shared Windows hosting with Plesk runs ASP.NET Core fine once you know the moving parts: the hosting bundle, the app pool, web.config, app_offline.htm, environment variables and folder permissions. A checklist that gets a .NET 10 app live.
A practical workflow for building a real ASP.NET Core site with Claude Code: write the brief first, scaffold with templates, work in small reviewed steps, encode rules as tests, and deploy in the first week.
