Testing and proof are complementary. Testing, including property-based testing and fuzzing, is powerful: it catches bugs quickly, cheaply, and often in surprising ways. But testing provides confidence. Proof provides a guarantee. The difference matters, and it is hard to quantify how high the confidence from testing actually is. Software can be accompanied by proofs of its correctness, proofs that a machine checks mechanically, with no room for error. When AI makes proof cheap, it becomes the stronger path: one proof covers every possible input, every edge case, every interleaving. A verified cryptographic library is not better engineering. It is a mathematical guarantee.
And in Pharo (and in all Smalltalk systems I know), these tools coexist without composing smoothly. They sit next to each other, but they don’t feel truly integrated in the way “IDE” suggests. The result is a workflow that can become chaotic: the tools reduce complexity (because they are powerful) and increase complexity (because the working set is hard to keep coherent).
。PDF资料对此有专业解读
전세사기 피해 501건 추가 인정…누적 3만6950건
DigitalPrintPrint + Digital