Home

Advertisement

Wed, May. 20th, 2009, 03:16 pm
observation

Code clarity results in performance gains.

Code "optimizations" result in bugs.

Knuth was right.

Wed, May. 20th, 2009 09:16 pm (UTC)
[info]patrick___

I have to admit that I've been following that programming philosophy more and more as time goes on. There's a time and place for optimizations, but it's only after you've got good, clear code design in place (and the optimizations need to be done in a way that doesn't destroy that clarity and good design).

Wed, May. 20th, 2009 09:27 pm (UTC)
[info]robkeeney

Yup. It's easier to make correct code fast [if needed], than to make fast code correct.

Advertisement