4 ms·
As soon as a significant portion of the time spent tackling a new feature or addressing a bug becomes reading code (which you may not have written) the types pa
by karatestomp 6y ago
As soon as a significant portion of the time spent tackling a new feature or addressing a bug becomes reading code (which you may not have written) the types pay off to at least[1] a 0.75x time-multiplier, and I'd say that's very conservative. It also makes it a hell of a lot easier and faster to collaborate on different parts of a feature that interact without exactly overlapping—"here's the interface I expect to implement, code to that, if anything changes TypeScript will tell you without our even having to talk (about that)"
[1 EDIT] at most? hahaha.