Original Summary

A couple of weeks ago, I was coding with Claude Code and other AI IDEs and got completely fed up. The agent kept declaring "task complete" with total confidence, but when I looked under the hood, backend routes were missing, UI buttons were unwired, or it was acting like a hero for fixing a bug it created 20 minutes earlier. I posted a raw rant about it on Reddit expecting maybe two upvotes. Instead, it blew up to over 21K views. The comments showed me I wasn't crazy everyone from weekend vibe coders to experienced prompt engineers was burning hours manually checking diffs because agents were basically grading their own homework. Instead of chasing outreach volume or spamming link blasts, I just started having deep 1-on-1 conversations in the comments and DMs with the devs who replied. We talked through their actual workflows, how they manually inspect commits, and what workarounds they'd tried building. Those deep chats shaped everything for us. Instead of guessing, we built a lightweight local CLI (malveon check) that auto-detects your plan and runs deterministic build, lint, and test commands before git commit. If a check can't be proven, it marks it as NO PROOF instead of letting an LLM guess a pass. We just released the v0.1.0 terminal build for free beta testing.   submitted by   /u/AlternativeLimit8551 [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/9/18 00:49:11