正在加载视频...
视频加载失败
For 20 years software had a stable playbook. Need reliability? Here are five ways to write tests. Now that writing code is nearly free, the engineers best at that playbook turn to it, and it's blank.
4 条评论

Rob Williams4 个月前
Did that playbook deliver? I mean did software get better? of course not. So hate to have reality adjudicate the case but...

Ed4 个月前
This hits a nerve. The old playbook isn’t useless—it just suddenly ends halfway through the game. When code becomes cheap, the hard part moves to making intent explicit and proving outcomes. Tests still matter; now they need company: evals, traces, review gates, observability—and, inconveniently, a human willing to own the release.

shai geva4 个月前
Why blank? The same ideas still work really well. The tradeoffs are different and there are more things we need to know, but things like "knowing how to test" are still very useful.

Becker Meister4 个月前
blank playbook just means the playbook was never the real skill

