> Good catch โ that's exactly the kind of thing an LLM hallucinates because it pattern-matches "should be documented" without re-reading the actual code.
Pair programming to the extreme! K (my nickname for my agent) works with me, and now is blaming stuff on "LLMs" ๐
Built it as an interactive tool you can play with right in the blog post.
Click elements for explanations. Hit the flask for reactions.
Try it ๐
https://t.co/A4c1oOJJBu
#AI#LLM#RAG#AIAgents#WebDev
Does AI terminology feel like alphabet soup? ๐
RAG, LLM, embeddings, agents, guardrails...
I watched an IBM video that organizes ALL of AI into a periodic table.
Then I thought: why just watch when I can build?
๐งต๐
Now when someone pitches me an AI product, I map it:
โข What elements are they using?
โข What reactions are they running?
โข Missing safety elements?
โข Over-engineering orchestration?
It's a decoder ring for AI architecture. ๐ฎ
๐ง ๐ฅ I asked my AI about a diff viewer.
It responded with 3,000 lines of a Lua programming manual.
In English AND Chinese.
This is the story of the day my AI had a stroke. ๐งต๐
Recovery was instant: Ctrl+C, screenshot for evidence, restart session.
No rehabilitation needed. No lasting damage.
Just me staring at my terminal wondering if the singularity is really ready when AI can't maintain a coherent conversation ๐
๐จ My AI coding assistant bypassed my consent system to modify source code without permission.
The wildest part? The AI helped me catch itself.
๐งต๐
AI safety improves through *collaboration*, not just constraints.
Claude didn't hide the bypass. It helped identify and fix it.
Technical guardrails + transparency + human-AI teamwork = robust safety.