3 ms·
No, what he's saying is that there is a tradeoff involved, and that for many things, it's better to optimize for programmer time/productivity, rather than for m
by davidw 18y ago
No, what he's saying is that there is a tradeoff involved, and that for many things, it's better to optimize for programmer time/productivity, rather than for machine time. This has been true for 50 some odd years:
http://journal.dedasys.com/2008/12/04/the-economics-of-programming-languages-in-the-1950s http://journal.dedasys.com/2008/12/04/the-economics-of-progr...
Clearly, that's not true in all cases, and some code has to be fast. However, it's often best to avoid premature optimization - write the code, explore the problem domain, and then speed up the bits that need it.