Re: On achieving goals (enterprise acceptance/coding guidelines)

At 06:59 AM 3/24/2002, James Tillman wrote:
>On Saturday 23 March 2002 03:43 am, Bas A.Schulte wrote:
> > The highlights in this respect are primarily "StudlyCase" and the use of
> > "getXXX/setXXX" on attributes:
>
>I find it hard to believe that use of StudlyCase and get/set would have such
>a big effect.  I think it's more the use of sane coding constructs in your
>code that will be the deciding factor.  I agree that the "line-noise" you
>refer to and which plagues even some of the best perl source code is the
>result of either programmers proud of their obfuscatory skills, or of their
>ability to twist around perl syntax for performance's sake (as in the
>Schwartzian transform).
>
>Any manager who would make the simple use of StudlyCase and get/set a
>prerequisite for acceptance doesn't have enough managerial skills to make me
>care whether he uses Perl or not.  He'll just switch to C# later on, anyway,
>when he inevitably gets borg'ed by Microsoft.  A good manager will be more
>interested in consistent coding style and design.
>
>Well written perl looks enough like Java to make this a moot point anyway, in
>my opinion.  And this is, of course, just my opinion...


I don't think this is true.

People read things comfortably that they are used to. I find having to slog 
through large amounts of code whose braces line up instead of the first 
brace being at the end of the construct to be harder to read because it's 
what I am used to.

I also find perpetual underscores a bit harder to read and pushes the lines 
out longer.

But I guess it just depends, I wouldn't really care either way. And I think 
the people who do mostly Perl prefer all underscores... but I have to say 
the braces is really the thing that I hate to see differently.

I think 9 out of 10 books I read does the braces where the first brace is 
on the same line as the command. So I guess this is just how I have gotten 
to deal with code.

I haven't read a lot of Python code, but I imagine it would take me a long 
time to understand because I would be trying to look for braces everywhere 
but instead have to look for indents as the cognitive cue instead.... and 
this would slow down my mental processing of the language. But eventually I 
would probably get used to Python I imagine.

And hey, I got used to VI, so I think I can get used to anything. :)

I also eat my toast butter-side up BTW.

Later,
    Gunther