Re:Dynamic type systems are not inherently more open
by hopia on Sunday January 19, 2020 @10:13AM
(#22091808)
Productivity can be really subjective. Those that are used to modeling the problem domain with the type system find that their most productive approach, even with prototyping.
[ Parent
| on HN ]
Re:Dynamic type systems are not inherently more open
by dllthomas on Sunday January 19, 2020 @02:06PM
(#22093204)
Right, and the type system is such a big help in refactoring - especially in small projects - that you don't have to be all that right in your first N cuts at the model. You can write code and find out where you're wrong, and fix it fast.
Re:Dynamic type systems are not inherently more open
by pwm on Sunday January 19, 2020 @02:51PM
(#22093546)
It’s even more help in larger projects :) The dividends of type-checher aid refactoring really start paying off once the project is above a a certain size/age.
Re:Dynamic type systems are not inherently more open
by dllthomas on Tuesday January 21, 2020 @05:04PM
(#22112161)
Yeah, I think I was unclear. Given a need to refactor, it's a bigger help on a bigger refactor.
But a large refactor on a large project is still a pain. By the time you get there, you still want your model stable and/or flexible enough that you don't need to do that much.
On a small enough project, every refactor is easy enough that you can lean into it. Make a bunch of assumptions you're not confident about, setting up the types so you're sure you'll know what needs fixing when they're wrong. Then you test those assumptions as you write - and run - more code.