2 ms·
> in the worst case we would have repeated definitions of these functions. Code that any junior developer will be able to safely reason about and change It's a
by int_19h 5y ago
> in the worst case we would have repeated definitions of these functions. Code that any junior developer will be able to safely reason about and change
It's also code that many junior developers will forget to change in all the places when they fix a bug in one of them.
- CraigJPerry 5y agoYeah 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.