5 Matching Annotations
  1. Jun 2026
    1. what changed after the December 2025 model inflection , and why "spec to pull request" is now becoming a real production workflow.

      'Spec to pull request' as a production workflow means the human's job becomes writing requirements, not code — a complete inversion of the current engineering process. The December 2025 inflection point is significant: it marks when models became capable enough to close the gap between high-level intent and production-ready implementation without constant human steering.

  2. May 2026
    1. Weirdly though, those things have started to blur for me already, which is quite upsetting. I thought we had a very clear delineation where vibe coding is the thing where you're not looking at the code at all. You might not even know how to program. You might be a non-programmer who asks for a thing, and gets a thing, and if the thing works, then great! And if it doesn't, you tell it that it doesn't work and cross your fingers.

      作者原本认为vibe coding和agentic engineering有明确界限,但现在发现两者界限正在模糊,这让他感到不安。

    1. LLMs accelerate the wrong part

      【洞察】「LLM 加速了错误的部分」——这句话点破了 AI 编程工具的根本问题:它们加速了代码的「生成」(原本不是瓶颈),却无法加速代码的「理解、审查和维护」(真正的瓶颈)。与 a16z 报告的「10-20x 生产力提升」数据对照:生产力的提升是真实的,但被提升的维度是否是最应该被提升的维度,是一个完全不同的问题。

    2. the more you rely on AI to write code, the less you're able to oversee what the AI writes

      ✉️【洞察·监督悖论】这是本周关于 AI 编程最深刻的一句话:越依赖 AI,越失去监督 AI 的能力。这是一个隐性的技能退化循环,与肌肉萎缩类似——不用则废。与 Uncle Bob「传统编程已终结」的乐观叙事正面交锋:如果开发者失去了理解代码的能力,他们还能做什么来保证 AI 生成代码的质量?