What I see among many plumbers is the notion that the world of algorithmic programming does not exist ("I dont give a $#@! about big Oh, algorithms are entirely unnecessary, I dont even know what quicksort is and I dont care LOL"). Similarly the other camp trivializes the act of plumbing. Neither do our craft any favors.
I mean, structured programming was much better than unstructured, goto-riddled, ball-of-mud programming, but... mathematical proof? Not with that foundation.
You can actually do formal mathematical proofs of functional programming (at least in the small). You can do it for structured programming, too, but in the much smaller.
Also, we don't have hardware that is functional all the way down (no pun intended, but it is somewhat unavoidable), so even a purely functional world must be built on something else. That better not be a ball-of-mud.
I think it's important to take this in context. EWD was a proponent of Computer Science as mathematical proof, and as such pushed hard for structured programming methods. This was the mid 80s.
In hindsight, we have learned that there are too many unknowables in true software engineering, so we need to be more Agile. Try something, fix it, and try again.
One of his big points in that paragraph is something that we should take to heart. Programming by cheap labor is very dangerous. We do need to think as well as test and do.