4 ms·
In my experience: a profiler, usually. Just because I can throw down a lot of code quickly doesn't mean I don't have the tools to analyze code when I go "hmm, t
by eropple 4y ago
In my experience: a profiler, usually. Just because I can throw down a lot of code quickly doesn't mean I don't have the tools to analyze code when I go "hmm, that seems slow".
- incrudible 4y agoThat works for big hotspots, but not for the tiny papercuts that make every little thing 10x slower.
- eropple 4y agoSure. That's a tradeoff you consciously make to get the thing out the door. That's what technical debt is. You pay it down later. (Or you go bankrupt and it doesn't matter anymore.)
- incrudible 4y agoThe blog post challenges the assumption that the slower version is any way improving productivity. At least for the given example, I agree.