[hbrn]

> most common reason for using static typing is to allow the codebase to be a monolith like it's still the 90s

This is so true. Static typing shines when you have a very complicated deeply nested system. And that's what most teams are naturally end up creating.

But how about not building the complicated system in the first place? Most of complexity in modern software is accidental.

[bombolo]

> But how about not building the complicated system in the first place?

"For every complex problem, there's a solution that is simple, neat, and wrong."

[hbrn]

Read it carefully. Complicated is not the same as complex.

[bombolo]

A person judging a solution he doesn't know to a problem he doesn't know… How well reasoned.