Comment by eterevsky
2 years ago
I'm not sure about "spending hours". In my experience it's more like "detect an error during compilation instead of an exception during execution". Once you see the exception, it's usually quite clear what exact property is misspelled. So strong typing saves a few second of execution and reduces the need for some types of unit tests.
It is always the thing you forget to unit test that causes the issue. Or the one code path that rarely runs, and causes a mysterious error once a month.