It's pretty strange that articles comparing static vs dynamic rarely mention team work. For example, we work on a feature, several engineers, everyone in their own branch, with always changing requirements and a lot of experimentation of course. From time to time I have to merge their work to the main branch. In PHP it was always an adventure because merge errors and conflicts (including some very silly ones) are often caught too late at runtime after the whole CI/CD cycle, and then you have to go again. Sure there are tests but they don't cover everything (and it's a nuisance to cover 100% including infrastructure layers if you are in the experimentation phase). PHP has linters but they're very slow and complicate the process. Now that we've switched to Go, merging (and generally team work) is a breeze. The compiler catches all problems immediately, our development time is much shorter now as we don't have to go back and forth with runtime errors.
This has never been an issur for me in my 13 years as a professional programmer, most of those in static languages. I prefer static typing due how it encourages good design and how in good static typed languages like Rust it id almodt always true that if something compiles then it also runs. But, no, merge errors have never been an issue for me with either dynamic or static.
I don't know why but I almost never experienced this as a big problem, especially with the current fashion of building independent services that don't grow too big. Maybe you guys are all working on the same files at the same time which is never fun?
I'm not saying what you're describing can't happen I'm just saying to me it's rare and I work with Ruby and plain JS.
