timdeschryver.dev valid

Tim Deschryver

Technical writing by Tim Deschryver, a Belgian software engineer and Microsoft MVP specializing in .NET, Angular, testing, AI-assisted development, and developer tooling.

For agents: Personal technical blog by Belgian engineer and Microsoft MVP Tim Deschryver on .NET, Angular, Playwright testing and AI-assisted development, with RSS feed.

playwrightdotnetangulartestingai-assisted development

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T15:49:35.168Z. Cached copy · Source on timdeschryver.dev

# Tim Deschryver

> Technical writing by Tim Deschryver, a Belgian software engineer and Microsoft MVP specializing in .NET, Angular, testing, AI-assisted development, and developer tooling.

The articles contain practical explanations, runnable examples, and lessons learned from building software. Every page is available as plain Markdown by requesting it with the `Accept: text/markdown` header, and every article also by appending `.md` to its URL; the links below point to the Markdown versions. Prefer a page's canonical URL (the same link without the `.md` suffix) when citing it.

## Main sections

- [Home](https://timdeschryver.dev): Author profile, credentials, and areas of expertise
- [Blog](https://timdeschryver.dev/blog): Long-form technical articles
- [Developer Bits](https://timdeschryver.dev/bits): Concise technical notes and examples

## Blog posts

- [Sprint Zero is about building momentum](https://timdeschryver.dev/blog/sprint-0-is-about-building-momentum.md) (2026-10-06; topics: AI, Team, Agile): Deliver value early and build stakeholder trust from Sprint Zero. Agentic AI and practical tooling help teams ship working features and act on feedback.
- [Scheduled AI in practice: turning telemetry into a daily health report](https://timdeschryver.dev/blog/scheduled-ai-in-practice-turning-telemetry-into-a-daily-health-report.md) (2026-08-20; topics: Azure, Application Insights, AI): How I integrate existing tools within the AI context to turn Application Insights telemetry into an actionable daily health report on a schedule. The report highlights what needs attention and starts a conversation I can continue, while I stay responsible for the next steps.
- [Testing AI prompts and comparing models with promptfoo](https://timdeschryver.dev/blog/testing-ai-prompts-and-comparing-models-with-promptfoo.md) (2026-07-29; topics: AI, Testing, Prompt Engineering, Promptfoo): Just like other software components, prompts benefit from tests that provide representative inputs to verify that the outputs meet the requirements. With promptfoo, you can test prompt behavior, compare models, and track output quality and keep runtime costs in check.
- [Your first MCP server with ASP.NET](https://timdeschryver.dev/blog/your-first-mcp-server-with-aspnet.md) (2026-06-25; topics: .NET, ASP.NET, AI, MCP): Learn how to query your application's data using natural language by building an ASP.NET MCP server.
- [Using Agentic AI to create your own component library](https://timdeschryver.dev/blog/using-agentic-ai-to-create-your-own-component-library.md) (2026-06-09; topics: Angular, AI): Agentic AI changes the trade-off between using an existing component library and building your own. This post explores how AI agents can help teams create, maintain, and evolve a custom Angular component library without taking on the full cost.
- [Running a production-like local environment with Aspire](https://timdeschryver.dev/blog/running-a-production-like-local-environment-with-aspi
…

Related sites

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=timdeschryver.dev · GET /v1/domain/timdeschryver.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for timdeschryver.dev:
1. POST https://agentwebmap.com/v1/sites/timdeschryver.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://timdeschryver.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/timdeschryver.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/timdeschryver.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.