"Some people do all of this on paper before writing a single line of code. Others plan by making types and interfaces, then proceed to implement those. I just l

"Some people do all of this on paper before writing a single line of code. Others plan by making types and interfaces, then proceed to implement those. I just like making prototypes." Of these, I sound the most like you - think just a little, then sit down and start coding to get a feel for things. Yet I find a good type system essential (or at least conspicuously missing when I write Python). There is a notion that, if one has static type checking, one has to get the types right before writing code. There's no reason that has to be the case. Get a sketch, start writing code, refine your sketch. With type inference, the sketch can even be somewhat incomplete and still help me find where my assumptions clash.