Vibe coder vs agentic engineer: brute-force testing versus just reading the code
ChainZenit · x · 2026-09-07
A widely-shared contrast on two ways to figure out what your code does:
- The vibe coder's way: run it on every platform, try every combination of env vars and user settings, check every admin panel and log, monitor all traffic to see where data goes.
- The agentic engineer's way: read the code.
Jimmy Koppel replied that for anything of complexity, reading is actually easier than running—his own vibe-coded apps are simple web projects without privacy or security requirements.
Related event: MIT researcher: reading code beats running it(4 posts)→
More from coding & agent
- Knowledge work is much harder for agents to automate than code, argues Matt Pocock — mattpocockuk · 2026-09-07
- SRMA: A Game-Theoretic Bilevel Approach Brings Convergence Guarantees to Multi-Agent LLM Systems — Yihang Chen · 2026-09-07
- What You Leave Unspecified Is the Agent's Free Variable: Paras Chopra's Framework — paraschopra · 2026-09-07
- Building a compounding AI workflow: bank context and rules so tasks never start from zero — oran_ge · 2026-09-07
- Google AI Search MCP server adds grounded web search via Vertex AI or Gemini — modelcontextprotocol · 2026-09-07
- Asterwise launches Vedic astrology MCP server with real ephemeris calculations — modelcontextprotocol · 2026-09-07