I said reliably. Without static types in large codebases you are likely to miss things. E.g. you rename a variable but don't catch everywhere you should have updated it.
Don't say "but tests".
I said reliably. Without static types in large codebases you are likely to miss things. E.g. you rename a variable but don't catch everywhere you should have updated it.
Don't say "but tests".
If your data model is open and not closed you only need to change the location you are changing. This is how the internet works. Types that don't support this model actively hinder refactoring.
Ifv you include the artificial restriction of not "use the correct tool/tests", then maybe you are right.