Hacker News Reader

A pragmatic engineering approach often beats the theoretic "correct" approach in most applications.

It does occasionally. In my experience, however, sometimes improving a pragmatic approach requires doing things correctly from the ground up. Sometimes the performance gain is worth it, sometimes it isn't. But generally it is there.

I don't entirely disagree. What I've found is that insistence on "correctness" is often confused with insistence on "minutiae". I suppose that in my experience the latter is usually what people mean when they talk about the former. The result is often lots of wasted resources and time fussing with tiny esoteric details that the end-user will never notice.

Correctness is certainly valuable. I've also seen projects go down long paths avoiding correct correctness due to time or resource constraints only to end up with an inferior product.

I guess a better conclusion is that a good balance needs to be struck. And I suppose that's ultimately the pragmatic approach, if the "correct" approach is better, do it, if the "get it done" approach is better, do that instead.

Reply on news.ycombinator.com