> that can mean that large projects can end up being less maintainable in the future because you don't usually have a type checker
That's not true if you seriously unit-test your code base, which you should in both cases.
That's not true if you seriously unit-test your code base, which you should in both cases.
Neither approach is wrong, but most developers have (sometimes very strong) opinions on which is the right way to do it in various different cases.