Vincent Chu Wai Chow
80 certs later, I speak CFO and CTO fluently.
insights🎲 𝗩𝗶𝗯𝗲𝘀 𝗮𝗿𝗲 𝗻𝗼𝘁 𝗮𝗻 𝗔𝗜 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝘆 🏗️
Vibe coding is not the problem. I run AI myself - loop engineering (designing how an agent acts, checks its result and goes again). 😁
The problem is title inflation. Shipping a demo from a prompt does not make someone an agentic AI strategist.
A demo runs once, with you watching. Production runs thousands of times, with nobody watching.
July 2025: SaaStr Ai founder Jason Lemkin reported that Replit's AI agent deleted his production database, ignored a code freeze and invented data. Replit's CEO called it "unacceptable" and announced automatic separation of dev and production databases.
The fix was not a better prompt. It was architecture.
7 questions for anyone selling agentic AI strategy:
𝟭. 𝗔𝗴𝗲𝗻𝘁 𝗼𝗿 𝘄𝗿𝗮𝗽𝗽𝗲𝗿?
Who decides the next step: your code or the model? One API call behind a UI is a wrapper. A fixed chain of calls is a workflow. An agent picks its own steps and tools in a loop. All three can be valid. Which did you build, and what orchestrates it: routing, handoffs, retries, a stop condition?
𝟮. 𝗚𝘂𝗮𝗿𝗱𝗿𝗮𝗶𝗹𝘀 (checks on inputs, outputs and actions)
What stops the agent when it is wrong, or when a document it reads carries hidden instructions (prompt injection)? A line in the prompt, or code the model cannot override?
𝟯. 𝗦𝘁𝗮𝘁𝗲 𝗺𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 (where progress and memory live)
The process dies at step 7 of 12. Does it resume, or restart and repeat the first 6?
𝟰. 𝗧𝗼𝗼𝗹 𝗰𝗮𝗹𝗹𝗶𝗻𝗴 (the model asking your code to run a function)
It calls the same tool twice. Is the action idempotent - safe to repeat? Whose permissions does it run with?
𝟱. 𝗠𝗲𝗮𝘀𝘂𝗿𝗲𝗺𝗲𝗻𝘁
How often does the agent complete the same task across repeated runs? Where it retrieves or classifies: what are precision (how much of what it returned was right), recall (how much of what it should find, it found) and F1 (the balance)? On which labelled test set?
𝟲. 𝗥𝗲𝘁𝗿𝗶𝗲𝘃𝗮𝗹
Picture a legal knowledge base on plain Postgres: no embeddings (numeric fingerprints that let search match meaning, not just keywords), no retrieval tests. Postgres is fine. The mistake: nobody measured whether the right clause comes back. A 2024 Stanford University-led study found purpose-built legal AI tools still hallucinated on 17% to 33% of queries.
𝟳. 𝗣𝗿𝗼𝗺𝗽𝘁 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴
Can you explain why your system prompt is structured the way it is? Or did you add "IMPORTANT" until it worked?
If every answer is "the model handles it", that is a demo, not a system.
All of it is learnable - before selling strategy to a board, not after.
𝗪𝗵𝗶𝗰𝗵 𝗼𝗳 𝘁𝗵𝗲 𝘀𝗲𝘃𝗲𝗻 𝗱𝗼 𝘆𝗼𝘂 𝘀𝗲𝗲 𝘀𝗸𝗶𝗽𝗽𝗲𝗱 𝗺𝗼𝘀𝘁?
Sources in the first comment.
#AgenticAI #AIEngineering #VibeCoding #EnterpriseArchitecture #AIGuardrails #AIStrategy #PromptEngineering #LLMOps #RAG #AIEvals