THE ENGINEERING NOTEBOOK
AI, software and the decisions behind them. Essays to think with. Experiments you can take apart.
Explore runtime asyncCode. Measured results. Visual explanations.
START HERE
Runtime async changes where suspension is represented. A real two-library .NET 11 lab shows smaller compiler artifacts and lower allocation on some paths, while a controlled suspension case resists a universal speedup claim.
One compiled C# assembly, two pinned runtimes, and nine allocation scenarios. Real IL, JIT listings and measurements show when an object disappears, when nullable boxing moves off the managed heap, and why a local delegate can still allocate.
A real .NET 11 trace reveals logical async chains, a short-process buffer trap and the limits of method mapping and observation-cost measurements.
THE READING ROOM
A public NuGet evidence tracker compares three actual function-invocation contracts across two pinned packages while leaving general compatibility unknown.
A real .NET 11 trace reveals logical async chains, a short-process buffer trap and the limits of method mapping and observation-cost measurements.
One compiled C# assembly, two pinned runtimes, and nine allocation scenarios. Real IL, JIT listings and measurements show when an object disappears, when nullable boxing moves off the managed heap, and why a local delegate can still allocate.
Runtime async changes where suspension is represented. A real two-library .NET 11 lab shows smaller compiler artifacts and lower allocation on some paths, while a controlled suspension case resists a universal speedup claim.
An engineering evidence pack can clarify uncertainty without pretending to decide the financial merits of an investment.
A real ASP.NET and Microsoft.Extensions.AI fixture compares two proposal paths through one validator, preserves every failed revision, and makes explicit review the boundary of accepted work.
Cheaper software creation can increase the value of choosing well, earning attention and accepting responsibility for maintained outcomes.
A small local reference makes admission, retry, journal state and shutdown observable; a compiled Azure candidate preserves the distinction between mapping and deployment.
A diagnostic agent’s read-only claim is tested through actual SQL permission denials, fixed query templates and evidence-based hypothesis rejection.
An agent can explain why it wants to perform an action without establishing that it may perform it. It can produce a well-formed tool call without establishing that the arguments are safe. It can report success without proving that the external effect occurred exactly once.
A real framework tool reaches SQL Server, where two Index Seek plans return the same answer while reading different amounts of data.
A versioned local deployment recipe records its prerequisites, owned resources, observed HTTP results and cleanup, making its verification date a claim about an actual run.
System boundaries, evaluation and decisions that need evidence.
Application behavior, data access and telemetry connected to a measurable hypothesis.
Product assumptions, operating responsibilities and questions worth investigating next.
