4 ms·

The problem is that even Fable still make trivial yet high impact mistake when let on their own, and then you'd need to read the whole code to catch them… Mean

by stymaar 2mo ago

The problem is that even Fable still make trivial yet high impact mistake when let on their own, and then you'd need to read the whole code to catch them… Meanwhile they are very good at implementating an explicit algorithm that you feed it to them.

theptip 2mo ago
The trick is to set up the harness so that the solution is easy to verify - you’ve profited as long as verification is cheaper than building, but ideally verification is close to automatic (not always achievable of course). Generally you want to include objective/repeatable outputs as citations. An example would be, if you invest in an awesome layered test rig (browser test, fuzz/property tests, very well reviewed unit/integration tests, etc.) then you should be able to add features by just reading the acceptance test and scanning unit tests.
- stymaar 2mo ago
  > then you should be able to add features by just reading the acceptance test and scanning unit tests. That “just” is bearing a lot of weight though as tests are often even longer than the code itself, in addition to being excruciating to review.