Re:“Clean” Code, Horrible Performance
by eropple on Tuesday February 28, 2023 @05:13PM
(#34975661)
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".
[ Parent
| on HN ]
Re:“Clean” Code, Horrible Performance
by incrudible on Wednesday March 01, 2023 @04:27AM
(#34980375)
That works for big hotspots, but not for the tiny papercuts that make every little thing 10x slower.
Sure. 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.)
Re:“Clean” Code, Horrible Performance
by incrudible on Friday March 03, 2023 @03:40PM
(#35014704)
The blog post challenges the assumption that the slower version is any way improving productivity. At least for the given example, I agree.