Regardless, Rich Hickey's last talk (last month at Clojure Conj) offered a counter argument, why ADTs are usually not the best way to organize software (as part of his larger discussion against static typing).
It depends on context
> why ADTs are usually not the best way to organize software
He clearly hasn't proven anything about his code.
Is that a bad thing? It seems like many people are able to write software that works well and gets the job done without "proving anything" about their code in the way you're describing. Personally, I'm fine with not proving anything if I can deliver quickly and everything works, but I'd like to be convinced otherwise if there's real value there.
It’s a mirage to which many have succumb but like in the desert most died of thirst trying to catch it.
Let's try not to make inflammatory statements.
Without abstraction enforcement mechanisms, an abstraction you have correctly implemented can still misbehave, because someone else has tampered with its internal representation.