@monoidmusician@tech.lgbt Basically: the reason that errors are being made to begin with.

The thing with static type checking is that it *looks* preventative from the perspective of "catching errors before you ship", but from the perspective of "when you make the error" it's actually *reactive*; you make the error first, and then the type checker needs to catch it.

I think there should be a lot more work put into the question of "how can we reduce the errors that developers make to begin with", through every aspect from education, to making errors visually/conceptually self-evident, to other angles that I'm sure I haven't considered yet.

Static typing is, *at best*, a very partial implementation of the "conceptually self-evident" part, and it really isn't good enough for me to consider it a truly systemic solution.