I find this quote to be interesting... "On the contrary: the programmer should let correctness proof and program grow hand in hand. Argument three is essential

I find this quote to be interesting... "On the contrary: the programmer should let correctness proof and program grow hand in hand. Argument three is essentially based on the following observation. If one first asks oneself what the structure of a convincing proof would be and, having found this, then constructs a program satisfying this proof's requirements, then these correctness concerns turn out to be a very effective heuristic guidance." Anyone else think that TDD is a close approximation of what Dijkstra was talking about in the quote? FWIW - I say this as a non-practioner of TDD.