Be sceptical of your own work (2009)
The counterpoint in software is that it&#x27;s still useful to temporarily solve a narrow problem - and never need to return to that issue. How do you denote that in your code?<p>I have used multiple dispatch where a sub-type is deliberately handled, and the rest is left with &quot;Nice try, you would have to implement that first&quot;, and tests in library functions with the same rude response. And I have used strictly defined grammars on the input. ... and I still have lots of TODO list items not correctly protected from in the code. What else do you use in non-trivial cases? Much deeper or beyond program argument checks?