STRONG STATIC TYPING, A HILL I'M WILLING TO DIE ON…

Summary from the TLDR Web Dev newsletter

Strong static typing is not just a good idea, but also almost always the right choice. It leads to fewer bugs, a better development experience, and clearer contracts between different pieces of code. Strongly typed projects are typically developed slower due to a higher learning curve and more boilerplate code. Not using types often leads to more time spent documenting and testing. Strong static typing lets you catch more errors at compile time rather than run time, which prevents bugs from ending up in the hands of customers.