ai
everything written here about llms in real work — calling vibe coding a dopamine trap, the guardrails i build instead, and three mcp servers in rust
i have written about this twice, nineteen months apart, and disagreed with myself in between. both posts are here, in order, because the disagreement is the interesting part.
what does this blog cover about ai?
in 2025 i called vibe coding the tiktok of programming — a dopamine trap, fast feedback substituting for understanding. i still think the diagnosis was right.
what i got wrong was the prescription. “don’t do it” is not a strategy when the tools are genuinely useful, so the later post is about what replaced it: hooks, blocked commands, and the fences that make an agent safe in a go codebase. the uncomfortable part of writing it was noticing that my original fix was the same mistake i keep writing about everywhere else — a check in the wrong layer, trusting an input one hop too early.
and the building side: three mcp servers in one cargo workspace with a shared toolkit, plus the one rule stdio protocols never forgive.
- building three mcp servers in rust with rmcp — one cargo workspace, three mcp servers, and a shared toolkit — plus the one rule stdio protocols never forgive
- vibe coding: the tiktok of programming — the dangerous dopamine trap of large language models in coding
related
the guardrails post is go — go — and the mcp work is rust — rust .