@swyx: working on a "take this vibecoded slop app and make it a production-ready, e2e tested, maintainable, parallelizable age…
Summary
A skill is being developed to transform a 'vibecoded slop app' into a production-ready, e2e tested, maintainable, parallelizable agent repository, resulting in a robust codebase after 103 commits over 16 hours.
Similar Articles
Deleting 19k Lines of Dead Compiler Code Without Trusting the LLM
作者分享了在一周内用 AI 辅助但不盲信 AI 的方法,安全删除约 19000 行编译器死代码的经验:先用静态分析界定范围,再让 LLM 标记 RED/BLUE 函数,并用独立的调用图工具交叉验证标记完整性,最终实现零回滚、零修复提交的清理。
Ask HN: How to deal with shipping AI-written code you don't understand?
A Hacker News discussion sparked by a Meta engineer's LinkedIn post questioning the growing practice of shipping AI-written code without fully understanding it, asking how developers cope with this new standard.
How to Trust Your Coding Agents More (2 minute read)
A practical guide on how to trust AI coding agents more, emphasizing an 'inverse pyramid' of effort: codebase improvements, static analysis, prose guidance, then human review. It links to Cursor's official plugins repo for installing agent-friendly tooling and workflows.
AI didn't replace developers. It replaced the part where we understood our own code
开发者并未被 AI 取代,但 AI 取代了「理解自己代码」的环节:代码由模型生成后无人真正读过,调试退化为把报错喂回模型。文章引用 Veracode 对 100+ 模型的测试(45% 生成代码存在已知安全问题),质疑这种「用理解换速度」的权衡是否会反噬整个行业。
@swyx: beautiful essay in this morning’s newspaper from Ben - read all about it https://dev.to/dailycontext/design-for-churn-5…
一篇探讨 AI 时代代码“churn”(频繁重写)观念转变的随笔:当编写代码的成本大幅下降,可抛弃的高质量“一年生”代码与稳定的“多年生”核心架构应被明确区分,churn 本身不是问题,问题在于承重部位的无计划变动。