The EF Core N+1 problem: 51 queries from one loop
A report loop that looks harmless sends a separate SELECT per customer through lazy loading. Real SQL logs, timings at three data sizes, and two fixes.
On learning C#, moving into software, and what a first job asks for.
RSSA report loop that looks harmless sends a separate SELECT per customer through lazy loading. Real SQL logs, timings at three data sizes, and two fixes.
Your first xUnit test doesn't prove the code works, it forces you to say what working is. Real dotnet test output, green and red, and how to read both.
Two models got the same prompt and both returned C# that compiles. One of them is wrong in 55 cases out of 2349 and never raises an error about it.
One US bootcamp charges the same for its classroom and its mostly self-study schedule. The price follows deadlines and people, not the material.
FormatReceiptLine used a null customer. FindCustomer, the method that created that null, already returned and isn't even in the stack trace.
Four route mappings in one Program.cs produce a working HTTP server. Real responses, real headers, and the two mistakes you'll hit on your first POST.
Adding one Console.WriteLine and re-running costs over six seconds, measured. One breakpoint stop hands you seven variables without touching the file.
The installer asks you nothing and takes a few minutes. The time goes into checking that the version answering your terminal is the one you think it is.
The compiler is not asking for a cast. It is telling you no route exists between these two types, and a different number covers the case where one does.
It doesn't start with picking a language. It starts with an honest hours audit, three real schedules, and the arithmetic of what a quarter buys you.