Prompt Engineering in Production Is a Systems Problem
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.
10 articles.
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.
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.
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.
Build an evaluation set from real production traffic, assert on properties instead of exact strings, and wire it into CI so prompt changes ship on evidence.
Dify and Flowise compared after running both in production — orchestration model, RAG depth, self-hosting cost, API reuse and upgrade risk.
LangChain optimises for agent chains and tool use; LlamaIndex optimises for ingestion and retrieval. Where each one actually saves you engineering time.
Measure first, then route, cache, shorten, batch, and quantize — a practical order of operations for cutting LLM spend without shipping worse output.
What Langfuse actually did for my LLM pipeline: trace capture, token accounting, online evals and self-hosting reality, including what I regret.