Use evals before changing prompts
Treat prompt changes like code changes: measure the behavior before deciding whether the edit helped.
Treat prompt changes like code changes: measure the behavior before deciding whether the edit helped.
Citations should point back to the retrieved evidence, not to sources the model guessed after answering.
How to make Microsoft Agent Framework behavior visible in production with OpenTelemetry traces, token usage, model calls, tool calls, Aspire local debugging, and Application Insights monitoring.
Embed a small typed Python capability in .NET when an HTTP service would be more boundary than value.
Keep Python AI code behind an HTTP boundary and let Aspire wire it into the local system.
Do not hard-code model routing decisions into application logic.
Use filters for eligibility and ranking for relevance instead of blending both concerns.
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.
Do not let prompt instructions decide what data or actions a user is allowed to access.
Reserve human approval for actions where a wrong call would actually matter.