3 ms·
If there's no safety when changing things, then you've failed to define and verify adherence to contracts along component boundaries, and the lack of a proper t
by vidarh 4y ago
If there's no safety when changing things, then you've failed to define and verify adherence to contracts along component boundaries, and the lack of a proper test suite.
I've certainly seen that happen in Ruby, but I've also seen that happen in every other language - most of them statically typed - I've worked with, as very few languages have type systems expressive enough to prevent it (and it tends to massively destroy productivity to try check everything strictly enough anyway).