AI Code Assistants: Cursor, Claude Code and Copilot in Production
Six months of AI coding assistants on a real .NET and Python codebase: where they genuinely help, where they generate noise, and what they cost.
Practical guides for AI agents, retrieval pipelines and GEO tooling. Every post names the model, the version and the step that failed first.
Step-by-step for agents, retrieval pipelines, workflow automation and GEO infrastructure.
4 postsTwo tools, same job. Here is where each one is faster, cheaper, or more annoying.
4 postsWhat a tool is like once the novelty wears off and the traffic arrives.
Latest
The prompt is the smallest part of the system. What determines output quality is the context, the constraints, the feedback loop and the evaluation set.
Read the guideSix months of AI coding assistants on a real .NET and Python codebase: where they genuinely help, where they generate noise, and what they cost.
Structure pages so generative engines can lift them — a 40-60 word direct answer, extractable facts, matching structured data, and crawler access.
Three ways to route across models, compared on control, fallback behaviour, cost control, observability and portability — including when you need none of them.
A working retrieval-augmented pipeline with chunking, reranking and an evaluation harness — plus the three failure modes that produce confident wrong answers.
bge-m3, gte, nomic-embed against hosted APIs: multilingual reach, long text, dimension cost, retrieval quality and the index rebuild trap.
Who writes this
I build and run multi-tenant AI content automation in production — agents, retrieval pipelines, and the GEO layer that makes them findable. Everything here was wired into a system with real traffic before it was written up.
Everything here is tested against a multi-tenant pipeline in production. No sponsored verdicts, no review copies unless the post says so.