Conversation

This Tweet was deleted by the Tweet author. Learn more

Replying to

After refactoring a non-trivial dynamically typed code base I'm convinced that "dormant" type problems are the worst. Anything that brings that number down is really helping even if it's not perfect.

Replying to

and

what do you mean "dormant"

Replying to

and

I would interpret it as errors which are currently not causing any problems because of how the code is currently structured, but will pop up as soon as you try to refactor or change the code in any other way. Is that what you meant

Replying to

and

Yes. The biggest problem was misunderstood propagation of errors and other special cases that were broken on change but failed much later. A variant type would make these obvious. In a dynamically typed system with insufficient tests it can really become archaeology.

12:21 PM · Apr 25, 2020Twitter Web App

Replying to

There's always the "easy now, hard later" thing, but DT languages can be the right tool. Mix and match. DT needs regression tests and probably some form of gradual typing. I still use Erlang a lot. I like the reflection and that it's simple. Dialyzer helps but it's not perfect.