Hacker News new | past | comments | ask | show | jobs | submit login

I write performance critical software for a living (industrial image recognition) and I often try to squeeze the last few percent out of an algorithm. But even in my case the by far largest part of code I write is not performance relevant at all. And there I prefer terseness and readability over performance. Yes, there can be some cases where I have to switch to a more efficient version later, because profiling shows a bottleneck where I did not expect one to be. But in my experience this has never been too big of a problem to sacrifice readability from the beginning in all places.



I wasn't discussing readability, but rather performance. The two are not mutually exclusive. Nor was I picking on the "last few percent" of performance--the shortcoming in speed of the "I in team" example is likely an order of magnitude or more. And it isn't fixable without modifying the API.


OK, I understand. I just think that performance can be neglected completely at many places.


Death by a thousand cuts.


That does not sound like a nice way to die. ;)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: