The youngins always learn the hard way.
The youngins always learn the hard way.
The field is extremely diverse these days, and tools that are appropriate for small data science teams may not work as well in enormous monorepos maintained by thousands of developers (and vice versa). What's missing from most discussions of static/dynamic typing is context—each career is unique and what projects you've worked on will have a huge impact on your perception of which is preferable.
Given different parameters, I'm sure the decisions would be different as well.
For writing an application or something that actually require design and libraries? Why bother? You need to be meticulous anyway, why not be meticulous in code?
The focus for me is on the tools and frameworks, not the underlying language. Show me a Typescript-based or Go-based language that can go from zero to production as fast as Rails with the same-sized team with no productivity loss, and I'd happily use it.