Middleware order is important
Place ASP.NET Core middleware in the order that matches routing, security, and endpoint behavior.
Dotnet
Nullable warnings are design feedback, not noise
Treat nullable warnings as pressure to make object state and API contracts clearer.
Pass CancellationToken through real boundaries
Thread cancellation through every expensive operation instead of dropping it mid-chain.
Prefer health checks that test dependencies deliberately
Health checks should say something useful about readiness without turning every probe into production load.
Prefer keyset pagination for deep lists
Use seek-based pagination when users move through large ordered result sets.
Run Python in-process from .NET with CSnakes
A quick tip for embedding Python directly into a .NET app with CSnakes when you want a small slice of the Python ecosystem without a separate API service.
Separate prompts from authorization
Do not let prompt instructions decide what data or actions a user is allowed to access.
Start independent tasks before awaiting them
Create unrelated asynchronous operations first, then await them together.
Use approval for side effects, not for every tool call
Reserve human approval for actions where a wrong call would actually matter.
Use file-based C# apps for small repo utilities
Use a single C# file when a repo utility is useful but a full project would be ceremony.