🔁 LINQ Pitfalls: The Query That Ran Twice
The query didn't run when you wrote it. It ran when you looked — and it ran again when you looked again. Deferred execution, multiple enumeration, and the boundary that quietly drags a whole table into memory. Most of these traps reproduce with a List<T> and no database at all.