// Topics / LLM
LLM
Definition
LLM coverage in this archive spans 35 posts from Jan 2023 to Apr 2026 and treats llm as a production discipline: evaluation loops, tool boundaries, escalation paths, and cost control. The strongest adjacent threads are ai, go, and architecture. Recurring title motifs include ai, production, llm, and stop.
Key claims
- The archive repeatedly argues that llm only creates leverage when it is wired into an existing workflow.
- Early posts lean on llm and patterns, while newer posts lean on models and production as constraints shifted.
- This topic repeatedly intersects with ai, go, and architecture, so design choices here rarely stand alone.
Practical checklist
- Define quality gates up front: eval sets, guardrails, and explicit rollback criteria.
- Start with the newest post to calibrate current constraints, then backtrack to older entries for first principles.
- When boundary questions appear, cross-read ai and go before committing implementation details.
Failure modes
- Shipping agent behavior without hard boundaries for tools, data access, and approvals.
- Optimizing for model novelty while ignoring reliability, latency, or cost drift.
- Applying guidance from 2023 to 2026 without revisiting assumptions as context changed.
Suggested reading path
- Start here (current state): The Best Model Is the Smallest One That Works
- Then read (operating middle): Architecting AI-Native Applications (Without the Delusion)
- Finish with (foundational context): LLM Integration Patterns That Actually Survive Production
Related posts
- The Best Model Is the Smallest One That Works
- Running AI Locally: A Practical Guide for Teams Who Care About Control
- Stop Fine-Tuning Models You Haven’t Bothered to Prompt Properly
- Reasoning Models in Production: A Practical Guide
- Picking an AI Model for Production (Late 2024)
- AI Cost Benchmarking: What Your Bill Actually Tells You
- RAG Retrieval That Actually Works
- How I Actually Test LLM Features
References
34 entries tagged “LLM”