Tired of inconsistent methods for quality assurance
I am not sure if quality assurance is the right term for what I’m trying to describe. As soon as you start something a little bit larger than the proof of concept project, you realise that something is wrong. The way you (I) handle potential errors is problematic in a couple of ways: Code that ensures that certain conditions are satisfied in your classes is cluttering your class methods. These are secondary concerns in terms of what your class is supposed to do, and having to read code that ensures that constraints on method parameters are satisfied is not nice. ...