Re: Long names are doom ?

["AG" <ang@xtra.co.nz>]

"Pete Thompson" <blackpete@nowhere.somewhere.anywhere.com> wrote in message
news:aqvfhtk583och27tjjaagpt783kn21c6sp@4ax.com...
> On Fri, 1 Jun 2001 15:38:58 -0400, "Marin David Condic"
> <marin.condic.auntie.spam@pacemicro.com> wrote:
>
> I hate to cross-post, but...
>
> <snip>
>
> >The only real gripe I've got with the C/C++/Java crowd about naming
> >conventions is that whole business of slurring everything together as if
> >space isn't useful. TheNamesLikeThis just annoy me! What? Underscores (or
> >hyphens or tic-marks or whatever the language uses...) are some kind of
> >blasphemy in the various sects of C-ism? That, and I never liked any
> >language or OS that was case-sensitive. (Note: This is personal taste and
I
> >won't even begin to try to justify it with science or logic. I hate it.
> >That's enough. Its settled. Don't get caught doing it when I'm in
charge.)
> >(Nice little bit of flame-bait there, eh? We can resurrect one of those
old
> >debates that keeps cropping up periodically, right? :-)

I guess you just did:)

>
> Methinks it would be far more productive to simply let the team members
get
> their job done rather than worrying about whether they're adhering to your
> personal tastes instead of theirs...

Well, they do need to talk to each other don't they? And how about the
project
manager just letting "the team members get their job done" ? I guess that
*would*
qualify as the perfect world:)

>
> Anyways, regarding the underscore.  I'm a C/C++ programmer (now learning
Java)
> and I don't like the underscore because of its location on my keyboard,
and it
> affects my typing speed.  C/C++ are terse languages.  Being terse allows
you to
> do more in a shorter period of time.

Like more erorrs? Do you really really claim that your productivity speed is
only
limited by your typing speed? You must be a very exceptional programmer if
your
productive speed is only limited by that ...

>  I like using the i++ statement instead of
> i = i + 1.   I like being able to code as fast as my train of thought
allows
> me, and having to pause to type out the underscores can throw me off.

Ummm, you are confusing things now - if you speak touch-typing, then
underscores
are no problem - any half-way competenet secretary can do that of course, no
problem.
However, that has nothing to do with the programming.

Besides, your example compares 3 characters to 5 characters (plus perhaps
two spaces
which shouldn't be needed as far as your theory is concerned) So, anyone
really cares
about the [fraction of a second] difference in typing speed as oposed to
hours of design
time?

>  Typing
> This_Is_A_Variable takes me far longer than typing ThisIsAVariable.

You must be a very bad typer then:) I note that the whole of your sentence
above contains just 3 underscores but 7 blank spaces. So, how come the
3 underscores took you longer then 7 spaces? Sure, technically speaking
hitting the space bar IS faster then the underscore. *** But *** is it
really
your contention that this is what limits the speed of software development?

>  Reading
> the code isn't much of an issue as long as you capitalize each word in the
> variable name.  Yes, 'Thisisavariable' would be quite horrible.

If only reading the code was as simple as that... You only need caps to read
the code? Cool...