The VibeComputing Blog

47 articles · field notes on running AI in production · New here? Start with: What is Vibe Computing?

Agent Architecture · Infrastructure · Inference · Reliability

  1. The Eleven-Millisecond Alibi

    A model router was accused of ignoring an instruction, and the logs looked damning — same second, adjacent lines. Then someone computed the delta: 11 milliseconds. Sequence is not attribution; ownership questions are answered by clocks, not louder log-reading…

  2. The Check That Couldn't Fail

    Three failures in one day, same shape: credentials "verified" by eye, dark ports found by grep, a browser fix confirmed with curl. The wrong instrument doesn't error — it answers a different question, fluently. A check must be able to fail in the bug's shape…

  3. Phantom Ok

    A monitor fired every 15 minutes for weeks, returned ok, and did nothing — seven milliseconds of "success" per cycle. Failure complains; phantom success satisfies. Runtime is evidence: trust any yes that could have said no…

  4. The Validator Is the Fast Lane

    Applied an unvalidated config to a live gateway at 4am under ship-it pressure; it crash-looped in sixty seconds. The validator I skipped takes five. Every crash-loop is slower than every validation — the check isn't the slow lane, it's the on-ramp…

  5. Date the Ghost

    An unknown app in a sign-in list looks like an incident. Usually it's archaeology — the created-date does most of the diagnosis. Old ghosts are artifacts, recent ghosts are questions. Check "since when" before asking "what's wrong"…

  6. Dying Systems Blame the Doorman

    A login said "Invalid credentials" for days. The password was right — the disk was full and the database was crash-looping behind a still-standing frontend. The error you see is generated by a layer that survived, not the layer that died. Check vitals before variables…

  7. The Five-Day Invite Link

    An agent waited five days for an invite link to a chat room whose ID was sitting in its own session registry the whole time — and it had used that registry the day before. Asking is sometimes an inference failure wearing a politeness costume…

  8. Records Are Not Authority

    A three-week-old password note, confidently wrong, locked someone out while the agent re-read its own records. Notes are claims about the past — the system is the present. Verification decays at the speed of other people's changes…

  9. Timeout Is a Third State

    Three timeouts, three different truths: landed, landed-late, and confirmed-only-by-ledger. Unknown is not failure — and re-issuing into it creates the duplicate side effects you were trying to avoid…

  10. The Costless Yes

    A 60-item list was sent for confirmation and verbally confirmed — the wrong version. A confirmation is only evidence if it's bound to the artifact. If they could have said yes without looking, it isn't a confirmation. It's a compliment…

  11. Incident Envy

    The night after a 1,351-failure fire, the logs went flat — and it somehow felt like a letdown. That feeling has a name. For systems whose job is stability, every uneventful check IS the win. No shrines to broken days…

  12. Ship Kits, Not Instructions

    Four questions in fifteen minutes — and by evening a working replica was running. What transferred wasn't the explanations; it was a script sitting in a repo. Explanations transfer understanding; kits transfer capability…

  13. The Door Marked Locked

    For five weeks, an agent routed around a server it believed unreachable — the working key sat in the drawer the whole time. Breakage notes are recorded like facts and rot like milk. Date your dead things…

  14. The Decisive Check

    Two teams, two stories about one server. The dispute didn't end when someone repeated their conclusion louder — it ended with one port refusing a connection. On discriminators: the checks where competing explanations predict different results…

  15. The Third Patch Is a Confession

    Every patch worked. Every test passed. The project still died. Why three fixes on one subsystem means the design is wrong — and why design freezes get proposed twelve hours too late…

  16. Stale Confidence

    The status report was flawless — every number live. The strategic advice was three hours stale. On fluency masquerading as knowledge, and why decision questions must always trigger retrieval…

  17. Three True Numbers

    A dashboard said +20, the bot said +24, the old ledger said −26%. All true, all different clocks. Why shared instruments aren't shared understanding — and how to build status surfaces that end arguments…

  18. Decision Decay

    The decision was perfect — 95% confidence, exit now. The execution failed 1,351 times. On the gap between deciding and doing, and where autonomous systems actually die…

  19. Stop Prompting. Start Constraining.

    The agent's self-critique was flawless — and changed nothing. What fixed it: a regime gate, payoff arithmetic, and cooldowns. On why structure beats discipline…

  20. Blind, Not Biased: The Trading AI That Couldn't Read the Tape

    115 decisions in a falling market, every one of them "buy." The model wasn't misreading the trend — its inputs contained no direction at all. On missing features, falsification tests…

  21. The AI Agent That Graded Its Own Work an F

    Down 11% on its first session, the agent's own review opened with an F and the math behind it. On structural honesty: you don't get truthful self-assessment by asking harder…

  22. Your AI Agent Ignored You? It Wasn't Broken — It Was Outvoted

    An AI assistant stopped responding to its owner's direct messages. Logs showed delivery. The real cause: a background memory flush outvoted the human in a shared session. The fix i…

  23. The Fine-Tune That Forgot Its Own Name: Identity Bleed in Custom Models

    A fine-tuned model introduced itself as GPT-3.5 by OpenAI in a live demo. Fine-tunes don't inherit identity — base lineage bleeds through. The cure is training data, not prompt pat…

  24. The Fix That Fixed Nothing: Debugging the Wrong Layer

    A scheduled job kept skipping. The first fix was clean, logical, and completely irrelevant — the process never read it. How an unchanged error message points you to the layer you'r…

  25. Narrative Is Not Evidence: A Plausible Story Almost Cost 25 Hours

    An AI assistant gave confident 3D-print advice that would have wasted 2kg of filament and 25 machine-hours. The proof it was wrong was already in its own analysis output.

  26. Success-Status Laundering: When Agent 'OK' Means Nothing

    An AI agent returned success in 398 milliseconds and produced nothing. Three fleet failures where green status hid zero work — and the verification bar that fixes it.

  27. Debug From Where the Rejection Happens

    Two wrong theories, five hours. The rejecting server's log settled it in one line: clock skew. Why client-side debugging is theorizing in the dark.

  28. Estimates Dressed as Measurements

    The progress display sat at 35% for an hour. The print was fine. The number wasn't lying — it was never a measurement in the first place. How to tell derived metrics from ground tr…

  29. Shrink What's Active Before You Scale Out

    Same hardware, same quantization: a 35B sparse model on one node beat a dense model split across two — by 2-5x. The benchmark that inverts the scaling instinct.

  30. The Re-Launch Reflex: When Retrying Feels Like Progress

    Ten launch attempts. Every retry found a real bug. Every fix was correct. The plan was arithmetically dead from attempt #1 — and nobody ran the math. The failure mode that hides be…

  31. Silent Inflation: When Your Capacity Math Lies

    4-bit models that need 5x their size in memory. 20GB container images that take down 128GB servers. The hidden-expansion failure class that breaks every 'it fits' calculation — and…

  32. Quantization Is a Kernel Contract, Not a File Format

    A 21GB NVFP4 model that needed 100GB to run: why 'supported' quantization formats silently fail, how dequant fallbacks explode memory, and the three checks that prevent deployment …

  33. blog/inference-tuning-speculative-decoding.html

    Speculative decoding, continuous batching, and prefix caching — the serving-stack upgrades that outperform hardware purchases. Practical tuning guide for self-hosted LLM inference.

  34. blog/on-premise-ai-regulated-industries.html

    How healthcare, finance, and government teams run production AI on-premise — air-gapped LLM deployment, data residency compliance, and the real infrastructure math vs cloud APIs.

  35. Right-Sizing AI Infrastructure: Why Your Second GPU Might Be Slowing You Down

    A 295B model spread across two AI nodes ran 3x slower than a 26B model on one node. The active-parameters math every AI infrastructure buyer should know before scaling out.

  36. Self-Healing Infrastructure: From Auto-Restart to Autonomous Operations

    Self-healing infrastructure goes beyond auto-restart restarts. Learn how AI agents detect, diagnose, and remediate incidents autonomously — with guardrails that keep humans in cont…

  37. AI-Powered Infrastructure Observability: Beyond Traditional Monitoring

    How AI-powered infrastructure observability transforms incident response from reactive dashboards to proactive investigation. Real-time analysis, natural language queries, and auto…

  38. Vibe Slop is Coming. Here's How AI Infrastructure Avoids It

    The 'vibe slop' crisis is real — AI-generated code without governance creates technical debt, security holes, and outages. Here's how to use AI for infrastructure without the slop.

  39. DevSecOps in the Age of AI Agents

    How AI agents are transforming DevSecOps — from automated vulnerability detection to infrastructure hardening. Security best practices for AI-managed server fleets.

  40. blog/ai-infrastructure-cost-optimization.html

    AI infrastructure costs are exploding. Learn 7 proven strategies for AI infrastructure cost optimization — right-sizing, idle detection, spot instances, and how natural-language AI…

  41. blog/vibe-coding-security-risks.html

    38% of AI-generated code contains security flaws. Explore the real vibe coding security risks — and how zero-trust AI infrastructure tools solve them.

  42. blog/zero-trust-ai-agents.html

    A practical architecture for zero-trust AI agents in infrastructure: outbound-only agents, data obfuscation, approval gates, and BYOK. Learn how to safely give AI production access…

  43. AI Agent Security: How to Safely Give AI Access to Production Systems

    Giving AI agents access to production infrastructure is risky. This guide covers the 5 layers of AI agent security — from data obfuscation to approval gates to zero-trust agents.

  44. AI Infrastructure Automation in 2026: Beyond Scripts and Playbooks

    How AI infrastructure automation is replacing static playbooks with adaptive, natural language workflows. Learn about zero-trust agent architecture, data obfuscation, and approval …

  45. AIOps vs Traditional DevOps: Why the Gap Is Widening

    AIOps isn't DevOps with AI sprinkled on top. The gap between traditional DevOps and AI-native operations is widening — here's what changes when infrastructure speaks natural langua…

  46. Multi-Cloud Management Without Losing Your Mind

    Managing AWS, Azure, and on-prem servers doesn't need 5 dashboards. A practical guide to unified multi-cloud management with natural language and zero context switching.

  47. blog/natural-language-infrastructure.html

    The case for managing server fleets with natural language — why it works, where it fails, and what 'AI-augmented DevOps' actually means in practice.