People often think about coding, but that's generally a small piece of it.
Typing is a form of structure, and especially a kind of documentation.
When encountering APIs of various kinds 'typing' is part of how they are expressed.
It's hard to build large monoliths without typing.
When working with 'wide scope' problems, when the typing is more oriented towards the data, that's another thing altogether, which is why I think for many systems untyped JS and Python works well enough there.
What most typed systems lack is a fluent way of mapping to 'data types' which are often external to the system, or at least externally defined.
> It's hard to build large monoliths without typing.
It's hard to build anything larger. In a microservice architecture one of the best things one can do is to define machine-readable schema (which is just a way to "type" RPC calls and messages) for all APIs/messages/events, and then auto-generate generate client code from it.
Most of the people who oppose typing must have been working on tiny projects, in small teams where they were co-authors of most of the code.
Typing is a form of structure, and especially a kind of documentation.
When encountering APIs of various kinds 'typing' is part of how they are expressed.
It's hard to build large monoliths without typing.
When working with 'wide scope' problems, when the typing is more oriented towards the data, that's another thing altogether, which is why I think for many systems untyped JS and Python works well enough there.
What most typed systems lack is a fluent way of mapping to 'data types' which are often external to the system, or at least externally defined.