Re: Arrays again - I must be dumb
- From: "Rhino" <no.offline.contact.please@xxxxxxxxxx>
- Date: Sun, 23 Apr 2006 19:14:17 -0400
"Greg R. Broderick" <terto@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:Xns97AE58EA6EBE9tnalzrqrfcrnxrnflarg@xxxxxxxxxxxxxxxxxxxxxxxxxxx
Mishagam <noemail@xxxxxxxxxxxx> wrote in news:5Dz2g.1160$n13.356I agree that style is very important but I don't think you can force newbies
@tornado.southeast.rr.com:
I also think he received a lot of style advices that look inappropriate
on this stage.
A LOT of professional software development revolves around programming
style. A class file can be absolutely correct, but if its style renders
the code unreadable and unmaintainable, then the code is worthless -- 75
percent of the cost of software over its lifetime is in maintenance. If
your code isn't maintainable, it is crap and I won't be recommending to
hire you! :-)
c.f. http://mindprod.com/jgloss/unmain.html
Coding habits (including style) are established early. The time to help a
potential software developer to learn good coding style (rendering them
potentially more employable) is early, at the same time that they're
learning the language and there are few or no bad habits to unlearn.
into a particular style until they have some idea of what they are doing. If
they don't know what the statements in the language do yet, it can really be
frustrating for someone to criticize their style too. I think they need to
get a basic understanding of the language and the concepts behind loops,
flow of control and so forth before you should start pressuring them to
adopt a good style.
Knowing exactly when they have reached the right point in their learning of
Java is not that easy and I'm sure each of us would put that point in a
slightly different place.
I also think that style evolves fairly constantly over time. Some basic
elements of Java style, like using capital letters at the start of class
names and lower case letters at the start of method names, should probably
be adopted very early on by a newbie. But other things, like how much work
to do in a method and when to create a new class, things which are more
design-oriented, evolve over the course of your work with the language as
you learn more about OO design. You certainly don't want to criticize a
newbie's design choices too early in the process of learning Java and you
certainly can't assume that they have already mastered OO design before they
start learning Java.
In the multi-pronged effort to learn what the statements in Java does, how
to design OO programs - and probably how the business he is in works - I
think a premature emphasis on style just undermines the confidence of the
newbie. Learning something complicated like Java is hard enough without
making the student feel inadequate because he doesn't use a professional
style in his first few programs.
--
Rhino
.
- Follow-Ups:
- Re: Arrays again - I must be dumb
- From: Chris Smith
- Re: Arrays again - I must be dumb
- References:
- Arrays again - I must be dumb
- From: janicethorne via JavaKB.com
- Re: Arrays again - I must be dumb
- From: Hendrik Maryns
- Re: Arrays again - I must be dumb
- From: Mishagam
- Re: Arrays again - I must be dumb
- From: Greg R. Broderick
- Arrays again - I must be dumb
- Prev by Date: Re: Updating from PointBase to Derby
- Next by Date: Re: Arrays again - I must be dumb
- Previous by thread: Re: Arrays again - I must be dumb
- Next by thread: Re: Arrays again - I must be dumb
- Index(es):
Relevant Pages
|
