>Regarding typing errors in production, I meant that we never encountered an error that could have been directly prevented by a Java-like static type checker[1], e.g., a function with an int parameter that was called with a string argument.
That's because your devs had already suffered this bug in their test runs once too many times, and killed it before it got to production.
That's because your devs had already suffered this bug in their test runs once too many times, and killed it before it got to production.
That, and luck.