|
![](/i/fill.gif) |
"Dan P" <dan### [at] yahoo com> wrote in message
news:4039335d$1@news.povray.org...
> Thank you, Warp.
Uh, I said that, not him.
> This has been a puzzle for me for some time now: why do so
> many programmers write such awful code?
It seems impossible for me to make a statement without people taking it too far!
I'm *not* saying all abstraction is evil and should be avoided, but I'm also
*not* saying everything should be abstracted as much as possible. I'm talking
about finding a balance between the two, according to the needs of your task.
There is never any excuse for writing code that is needlessly difficult to read,
such as many unproffessional coders like to do in the flawed belief that it
makes them look clever.
However, there is good reason to sometimes write code that makes it harder to
see the overall structure if doing so provides you with some other useful
information. Obviously a balance must be found and that balance is different for
different applications, but in my work it is useful to avoid a lot of
abstraction.
--
Tek
www.evilsuperbrain.com
Post a reply to this message
|
![](/i/fill.gif) |