2 ms·
Well the article is about speed of development, not the speed at which the code runs. Over the years I’ve come to embrace moving fast and writing code quickly,
by Aurornis 2y ago
Well the article is about speed of development, not the speed at which the code runs.
Over the years I’ve come to embrace moving fast and writing code quickly, even if it’s not the fastest. The faster I get the big things done, the more time I can spend optimizing what matters after I’ve identified it and determined it’s valuable.
- inglor_cz 2y agoThere is an overlap. Writing for PHP, I used to spend a lot of time waiting for Xdebug to trigger. Once the author released version 3.3, the improvement was so big that my own productivity went visibly up.
- branko_d 2y agoOn the other hand, some of the biggest performance wins come from the architectural choices, and those are often done before most of the code is written.
- whstl 2y agoYep, same experience. "Some of the biggest performance wins" in both developer speed and processing speed.