Formal verification and other protections resulting from strong static typing are less popular probably because of their delayed gratification effects - they're

Formal verification and other protections resulting from strong static typing are less popular probably because of their delayed gratification effects - they're seen as unnecessarily constricting in small projects and their benefits are only seen as projects are grown and maintained over long periods of time, so it's difficult to justify their use early in the project when the decision is initially made. I think that it's easier to justify rigor in traditional engineering projects (i.e. civil engineering) where project delivery dates are necessarily far off in the future - if you need to delay gratification anyway then you might as well adopt a more rigorous process. But in software engineering, where you can start delivering almost immediately, it's more difficult to get project owners and managers to see the value of rigor, especially if the project isn't yet known to have a long lifetime.