That is pretty funny but on a serious note I used eiffel which has similar pre/post-conditions mindset, and because pre/post-conditions in both are executable r

That is pretty funny but on a serious note I used eiffel which has similar pre/post-conditions mindset, and because pre/post-conditions in both are executable rather than statically proven as in CS theory, their efficacy is pretty much up to the user. Vigil gutting your source when you make a mistake would prove an effective motivation though! I actually like that and would actually be prepared to give that kind of thing a try (backed up with version control of course)! I use assertions pretty heavily in my code anyway but strong static typing does most of the heavy lifting and I'm grateful for it. The company ultimately dumped eiffel (that was ~20 years ago) because it had promise and hype but little else. Pre/post-conditions remain as a framework for thought as much as for coding.