I don't find dynamically-typed languages productive at all once the program gets past about 400 lines and/or you figure out what you need to do. The break-and-

I don't find dynamically-typed languages productive at all once the program gets past about 400 lines and/or you figure out what you need to do. The break-and-follow-the-errors approach is very powerful. It's usually not hard to find the exact break that will show you all the things you need to change, and then just work through them. My record is 5 days without buildable code, working in C++; once I'd worked through all of the errors, the program worked, and without any non-obvious problems. I miss this a lot when working in a dynamically typed language. (Thing by Jonathan Blow that touches on this: https://web.archive.org/web/20140929232443/http://lerp.org/notes_4/index.html https://web.archive.org/web/20140929232443/http://lerp.org/n...)