your paraphrasing of rich's thoughts seems like he is missing what type driven development is really about, and that is domain driven development. the idea behi

your paraphrasing of rich's thoughts seems like he is missing what type driven development is really about, and that is domain driven development. the idea behind letting types lead the way is not to just blindly rely on static types. it's old news that that is only a first approximation to writing good code. what types in sane languages (like f#'s records, discriminated unions, units of measure, classes, functions, etc.) allow is for you to model your domain in a clear way in code such that your programming becomes much more concise and clear as to what it is doing. the fact that static types try to link up everything is a side effect of that process.