Yeah that’s what i was getting at with: >> Code that has utterly obvious risks (you might introduce a differing behaviour in one implementation of Take() for e

Yeah that’s what i was getting at with: >> Code that has utterly obvious risks (you might introduce a differing behaviour in one implementation of Take() for example) - so obvious that it’s trivial to defend against with nothing more than generative testing. Really obvious risks are usually easier to handle than more obscure ones.