begin quoting kelsey hudson as of Sun, Jun 04, 2006 at 02:57:59PM -0700:
> Lan Barnes wrote:
> >I have an even better idea: Avoid clever algorithms altogether. Oh,
> >wait, that wasn't my idea ... it was from Kernighan and Plauger in "The
> >Elements of Programming Style."
>
> So now we stifle creativity for readability? Just put a comment.
Simplicity often takes more creativity than complexity. It's more
work to write something readable than not.
How can I tell if you're being creative if I can't read it? How do
I distinguish between creativity and plain old sloppiness?
> Or, if
> you can't understand it, think harder. I haven't come across a piece of
> code yet I couldn't understand after 15 minutes of, "ok, now just *what*
> the hell is going on here?" Then again, I find myself *thinking* in code
> sometimes.
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it. -- Brian W. Kernighan
--
_ |\_
\|
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
