译文语言

精益，而非背压

Lucas Costa 撰文探讨如何构建能应对代码生成机器人的系统，但文中将其称为"背压"的比喻并不准确。背压指的是向上游进程发出信号，告知其运行过快、需要减速；而 Costa 的建议更多是要求上游进程改变做事方式，而非单纯放慢速度。这关乎确保向下游传递足够的"质量"而非"数量"。作者认为，精益制造中管理不稳定输入的哲学才是更恰当的类比。

相关报道

I Am Not a Reverse Centaur
4.0
The author rejects becoming a "reverse centaur"—a term for humans forced to review machine-generated code—after observing a surge in LLM-produced pull requests to his open source projects. Despite his personal decision not to use generative AI coding tools, he now spends increasing time reviewing code written by AI and explains how he resists this role.
I can never fully embrace LLMs for code
3.0
The author, who once advised his sister to use code libraries without fully understanding them, now finds himself unable to commit AI-generated code he doesn't fully comprehend. He recounts spending 10 hours fixing code that an LLM produced in 12 minutes, and notes that while others trust AI code generators like a car engine, his need to understand every line negates any productivity gains.
Please, use a link!
2.0
The article argues that many single-page app developers misuse divs or buttons with onclick handlers instead of proper anchor tags for navigation, breaking browser history, accessibility, and native link features. The author urges using native `<a href>` elements or framework Link components.
Nontrailing separators do not spark joy
2.0
The article argues that disallowing trailing (or leading) separators in languages like JSON, Haskell, and Prolog was a design mistake, as it makes adding or removing elements more complex. It highlights languages like Python, Go, and Alloy that permit trailing commas, and notes potential parsing ambiguities when trailing separators are used in control-flow contexts.
How can I schedule work on a thread pool with low latency?
1.0
The article explains that the Windows thread pool is optimized for throughput rather than low latency, which can cause delays in task execution. It discusses the trade-offs between throughput and latency when scheduling work on thread pools.

精益，而非背压

I Am Not a Reverse Centaur

4.0

The author rejects becoming a "reverse centaur"—a term for humans forced to review machine-generated code—after observing a surge in LLM-produced pull requests to his open source projects. Despite his personal decision not to use generative AI coding tools, he now spends increasing time reviewing code written by AI and explains how he resists this role.

I can never fully embrace LLMs for code

3.0

The author, who once advised his sister to use code libraries without fully understanding them, now finds himself unable to commit AI-generated code he doesn't fully comprehend. He recounts spending 10 hours fixing code that an LLM produced in 12 minutes, and notes that while others trust AI code generators like a car engine, his need to understand every line negates any productivity gains.

Please, use a link!

2.0

The article argues that many single-page app developers misuse divs or buttons with onclick handlers instead of proper anchor tags for navigation, breaking browser history, accessibility, and native link features. The author urges using native `<a href>` elements or framework Link components.

Nontrailing separators do not spark joy

2.0

The article argues that disallowing trailing (or leading) separators in languages like JSON, Haskell, and Prolog was a design mistake, as it makes adding or removing elements more complex. It highlights languages like Python, Go, and Alloy that permit trailing commas, and notes potential parsing ambiguities when trailing separators are used in control-flow contexts.

How can I schedule work on a thread pool with low latency?

1.0

The article explains that the Windows thread pool is optimized for throughput rather than low latency, which can cause delays in task execution. It discusses the trade-offs between throughput and latency when scheduling work on thread pools.