Skip to content
← Topics

Verification

Confirming that what was produced is actually correct. Generation got cheap; this did not, and it is now the constraint.

Also called the verification gap

Producing a candidate implementation now costs very little. Establishing that it is correct still costs about what it always did, and we have to do it much more often.

That gap makes tests more important and turns evaluation design into senior work. It also makes the reviewer a bottleneck. "It works" means little when nobody can say what was checked.

I can produce several times more code than before. My capacity to confirm that code is correct has barely changed. Most of my current problems fit somewhere inside that gap.

See also Comprehension debt and The control arm.

Linked from