April 13, 2026
Ratatoolie vs Robo‑coders
Write less code, be more responsible
Dev world splits: hand‑coders vs bot buddies—who wins
TLDR: An engineer says use AI sparingly: let bots handle tedious tasks while humans stay accountable. Comments split between proud no‑AI purists, config‑first minimalists, and skeptics warning AI accelerates junk—an urgent debate as “vibe‑coded” apps flood feeds and quality control becomes the new battleground.
A developer confessed the AI talk is exhausting, but says the new normal is using bots for the boring bits and taking responsibility for the final product. They tried handing full control to an AI, then felt like an illiterate passenger; switched to reviewing every change—and suddenly life became “full‑time code reviewer.” Cue the meme wave: “vibe coding” (letting AI riff code by feel) vs. doing it by hand, plus a Ratatouille joke about having “a rat under my hat.”
The comments went full split‑screen drama. On one side, the craft crew: agentultra proudly ships a solo game in C, no assistants, “Wasn’t that hard,” proving slow‑and‑steady still slaps. On the other, the minimalists: chillaranand says just use config‑only tools and “avoid code as much as possible,” literally living the “write less” life (link). Then came the doom clarion: stratts warns it was always easy to crank out junk, now it’s easier—see the infamous TerrariaClone—and bots’ “code comprehension superpowers” can hide messes. The safety squad chimed in with receipts: qudat linked a careful, test‑first mindset in Thinking Slow, Writing Fast.
Bottom line: Everyone agrees on shipping responsibly, but the path splits—hand craft, config‑first, or AI‑assisted with rigorous review. The only thing growing faster than vibe‑coded apps? The comment flame meter.
Key Points
- •The author experimented with AI-assisted programming, initially using GitHub Copilot for completions and code generation.
- •A more extensive trial with Codex was conducted while building a terminal UI (cargo-tree-tui) for cargo’s tree command.
- •Giving AI broad control led to confusion; a shift to commit-by-commit AI assistance with thorough code review improved understanding.
- •The current approach is to use AI for tedious or slow tasks, write the engaging parts manually, and perform a final quality review.
- •The author plans to be transparent about AI usage and observes a surge in new tools that makes curation difficult.