Yeah the error list is my friend. Typos, assigning something to the wrong thing or whatever is fixed without having to run the code to test it. Just check the error list and fix any dumb mistakes I made before even running the thing. And I can be confident in re-factoring, because renaming something is either going to work or give a compiler error, not some run-time error which might happen in production weeks later.

Even when you're using a dynamically typed Lang you should be using all the appropriate scanners and linters, but so many projects just don't.

I joined a large project half way through and I ran pylint and stared as the errors (not just style stuff) poured out...

It's much easier to work with streams of untyped data in a weakly typed language.

I do believe that static typing is at least a local optimum, but I am still not entirely convinced. Rich Hickey is a very convincing presenter and I can’t help but think that he is on to something — with Clojure the chosen direction is contract-typing, which is basically a set of pre- and post-conditions for your functions that are evaluated at runtime. Sure, it has a cost and in the extremes they are pretty much the same as dependent types, but I think it is an interesting direction — why should my function be overly strict in accepting a “record” of only these fields?

true but i dont think is really a hot take?

Dynamic languages are good for prototyping, especially if a lot of libraries available