IDisposable and IAsyncDisposable make lifetime management feel pleasantly local: acquire something, use it, dispose it. That model is reliable when the acquired value has exclusive ownership of an independent resource.
It becomes dangerous when seve...
Pagination is often introduced as a performance improvement: fetch fewer rows, render less markup, and keep response sizes predictable. That is only half the job.
For an operational queue that changes while people work, pagination also defines what ...
Framework warnings are useful because they compress hard-earned experience into an early signal. But a signal is not an invariant. In an extensible EF Core architecture, design-time tooling can legitimately see less of the model than the running appl...
A routed page can compile, pass its authorization checks, have documentation, and still be functionally absent. If the people entitled to use it cannot discover a normal way in, the product behaves as though the capability was never built.
That is e...
A retry can duplicate a side effect even when the original command completed successfully.
This is easy to miss in a method that does two ordinary things: save a record and send a message. Each operation is understandable on its own. The difficult p...
Software is very good at making a calculation look authoritative. Give a rule engine enough inputs and it can return a crisp result in milliseconds. In a consequential workflow, that neatness is dangerous: a computed recommendation can quietly become...
An automated test is useful only when its assertion represents the rule we intend to preserve. That sounds obvious until a test passes for the exact condition that should make a reviewer uneasy.
A recent Blazor change offered a concrete reminder. Tw...
“Make it work offline” often turns into a storage task: serialize the last successful response, read it when the network fails, and move on.
That is necessary, but it is not the hard part.
The hard part is deciding what the stored response means ac...
Page numbers feel harmless. They are familiar, easy to render, and easy to explain. But on a mutable work queue, they can lie.
Imagine a reviewer reading a newest-first queue. They load the first 25 items. Before they request the next page, a new it...
Framework warnings are valuable because they turn hidden risk into visible friction. But a warning is still an interpretation of the evidence available to the tool. In a modular application, the command-line process may not load the same assemblies a...
Security integrations often fail in a surprisingly polite way. The library loads. Initialization succeeds. The function returns. Nothing crashes. Yet the protection we expected may not have participated at all.
That distinction matters when an appli...
SingleOrDefault looks like a small query choice. In practice, it is an assertion about your data model: for this predicate, zero or one row may exist.
That assertion is valuable when storage enforces the same rule. When the database permits duplicat...
A notification badge looks like a small feature. In a distributed application, it can expose a large architectural assumption.
I recently investigated a badge that sometimes stayed stale in an ASP.NET Core and Blazor application running across multi...