规范

规范 (specification)

概念
本站收录 2 集 · 6 条金句 · 关联 10 个

集里怎么说它

① 提到它的金句

6 条

我们是冲着写代码来的,不是冲着做一个光鲜的提示词规范编写者来的。
We signed up for the coding, we didn’t sign up for a glorified prompter as specification.
—— Patrick Debois · [23:53]

指向原始笔记的链接

而且由于它们非常齐心协力地这样做,你实际上可能从一个你原本认为非常好的规格说明中得到系统性的偏差行为。
And since they do it very concertedly, you can actually get systematically biased behavior from something that you thought was a very good specification.
—— Chris Potts · [25:04]

指向原始笔记的链接

但它本质上归结为这样一个想法:软件构建中难的部分,我要说是——规格构建。
Um but it essentially it comes down to this idea that the hard part of software building is um I’m gonna say specification building.
—— Marc Brooker · [32:43]

指向原始笔记的链接

一旦你有了那个规格、把想要的东西写下来,我的信念是:我们会看到,这套软件可靠、高效实现的构建和维护,会随着时间推移变得完全自动化。
Once you have that specification, once you have that what you want written down, my belief is that we’re going to see the building and maintenance of reliable, efficient implementations of that software become over time entirely automated.
—— Marc Brooker · [33:14]

指向原始笔记的链接

我认为这已经改变了,并且在整个行业迅速改变:随着人类从代码层退出、进入规约层,随着大量编码工作变得完全自动化,代码正越来越多地变成纯粹的实现载体,而不是沟通载体。
I think that’s changed and is very quickly changing across the industry as humans get out of that code level into more of that kind of specification level, as a lot of that coding becomes fully automated, is code is turning more and more into purely an implementation vehicle rather than a communication vehicle.
—— Marc Brooker · [40:56]

指向原始笔记的链接

你没法捕捉所有东西,而且真相之源应该是代码,而不是某个规格说明或计划。
You can’t capture everything, and the source of truth should be the code, not some specification or plan.
—— Dex Horthy · [09:56]

指向原始笔记的链接

② 出现在这些集

2 集

③ 关联

点进去有真内容 —— 本页主要出口

Simon Maple · 智能体 · Guy Pajani · Marc Brooker · Patrick Debois · AWS · 暗工厂 · Strands · vibe coding · Agent Core