I simply question writing projects using a monolithic style in the first place. Anytime somebody brings this up as an advantage of static typing I get a little suspicious. In fact, it could be argued that static typing gives the user enough rope to hang themselves with.

With dynamic typing you're much more likely to break things up early precisely because you know you have to keep things in your head.

On the other hand, static typing allows you to just keep adding code and it makes sure that the code will compile and run. However, at some point you end up with a large and complex system that you don't really understand. All you know is that it's self consistent. Understanding what the business logic is doing and why can be quite difficult and the fact that it type checks does little to help you there.

Coincidentally this is the reason that static typing proponents are obsessed with refactoring. Once you realize what mess you got yourself in then you have a ton of code to refactor and there's no way you can keep track of it all in your head.

With a dynamic languages refactoring tends to happen in much shorter cycles and introduces much less cognitive load.