|
|
Posted by Tim Streater on 12/15/06 10:34
In article <mhhgh.21433$f15.7579@fe09.usenetserver.com>,
Double Echo <doubleecho@your.com> wrote:
> It might be easier for _you_, but not for the next poor bastard that will
> have to agonize at the shitmess you made.
My code is carefully laid out, thank you.
> There is no excuse for shitty-looking code. Another annoyance for me are
> people
> who have to roll-up their brackets as if there is a line penalty for good,
> structured
> code. Like you're going to run out of lines or air or something.
>
> People who like to
>
> if (...) {
> }
>
> or
>
> while(...) {
> }
>
> annoy the fuck-out-of-me because I have to stop, read really slowly and try
> to grasp
> the nesting, and logic. It's all rolled up so you can't hardly separate the
> code into
> something readable.
>
> It's so much cleaner to
>
> if ( ... )
> {
> code here
> }
>
> or
>
> while( ... )
> {
> code here
> }
Funnily enough I completely agree here. If the braces are lined up then
matching braces are so much easier to find.
> but all the goddam schools preach shitmess roll-up coding and OO. It works
> but it's so fucking
> messy. You fucking kids think it's cool code, and wow, neato, but then
> somebody else has to
> work on it, and it's a fucking nightmare. Clean code, nested, and properly
> written will allow
> the code to be debugged better, and probably survive being re-written all
> over again because you
> can actually read it. I've gone on to delete code I can't read and just
> re-wrote it cleanly.
When what you are dealing with is spaghetti this may well be necessary.
-- tim
Navigation:
[Reply to this message]
|