Path: csiph.com!usenet.pasdenom.info!dedibox.gegeweb.org!gegeweb.eu!gegeweb.org!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail
From: Gene Wirchenko <genew@telus.net>
Newsgroups: comp.lang.java.programmer
Subject: Re: proper use of .java files (layout)
Date: Tue, 18 Dec 2012 10:40:40 -0800
Organization: A noiseless patient Spider
Lines: 86
Message-ID: <7sd1d8d54icvgpcvolc8uvr78ocelu96r1@4ax.com>
References: <e32ed4f5-58a8-4b3b-9868-d856db8141a8@googlegroups.com> <41e38b5a-2aa7-43a4-9bc8-87e0eb4a977c@googlegroups.com> <j7CdnSO05fKoG03NnZ2dnUVZ8uudnZ2d@bt.com> <kaq4d4$3o2$1@dont-email.me> <ytGdnR7BuNPoBE3NnZ2dnUVZ8lmdnZ2d@bt.com> <tb91d8tlal57qttm8n5tmjmuek1b8rv26m@4ax.com> <BYCdnT1W2siqN03NnZ2dnUVZ7tqdnZ2d@bt.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Injection-Info: mx04.eternal-september.org; posting-host="95789bcd602b4527561dc0cb1c85cae5"; logging-data="32161"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19Cdoq3BC0MepMaSLpQG4Rj77ZYUN16PVk="
X-Newsreader: Forte Agent 4.2/32.1118
Cancel-Lock: sha1:EQzwCBACb+VawGU97SPSwpNKMzw=
Xref: csiph.com comp.lang.java.programmer:20461

On Tue, 18 Dec 2012 17:39:02 +0000, lipska the kat
<lipskathekat@yahoo.co.uk> wrote:

>On 18/12/12 17:21, Gene Wirchenko wrote:
>> On Tue, 18 Dec 2012 16:27:28 +0000, lipska the kat
>> <lipskathekat@yahoo.co.uk>  wrote:
>>
>>> On 18/12/12 16:07, Eric Sosman wrote:
>>>> On 12/18/2012 10:05 AM, lipska the kat wrote:
>>>>> On 18/12/12 14:32, infinitum3d@hotmail.com wrote:
>
>[snip]
>
>>> Yes, start writing code
>>> What do you suggest he does, Sit there twiddling his fingers.
>>
>>       I suggest that designing comes before writing code.
>
>I agree ... but if you are suggesting that you do all the designing 
>before you start to write a line of code then I humbly suggest that that 
>approach is fundamentally and profoundly flawed.

     No, but I do design code before I write it.  The big design comes
first, then pieces of smaller design, then the code associated with
the smaller design.  Repeat the last two steps as needed.

>Just IME mind you, I'm sure you are not suggesting that.
>
>Actually I suggest that they proceed in parallel.

     For a given piece of code, design comes first.

>>> I bet you have a pre-meeting meeting to discuss what to discuss in the
>>> meeting don't you. Ye gods and little Indians, I've battled with the
>>
>>       Straw man
>
>Cheese sandwich

>>       No, but I do work out what is needed in terms of features and
>> then work out the sorts of entities that I will need to implement
>> these.
>
>Entities, hmm, a word heavy with meaning to anyone who has ever written 
>EJBs. We deal in Classes, packages, components and Interfaces in Object 
>Oriented software engineering with Java, entities reflect persistence 
>schemata.
>
><Makes sweeping statement then withdraws to safe distance>

     Or simply a word meaning something of interest.  If code, it
might be a class or a procedure.  It might also be who is using the
system, the hardware required, and so.  It could also be things one
must consider such as privacy laws.

>>> likes of you all my professional life. I always deliver though because I
>>> get code down and learn from it.
>>
>>       I write code, too, but the measure of a system is not just the
>> code.  Its organisation counts for a lot.
>
>Concur
>
>>
>>> Write code, make mistakes, refactor, reiterate ... LEARN
>>
>>       Or one can design and make far fewer mistakes.
>
>Well this depends on your approach to design doesn't it (see above)

     Of course.  How could it be otherwise?

>>> Or sit on your hands lamenting your inability to get past the first obstacle
>>
>>       Another straw man.
>
>Egg mayo on Rye, easy on the mayo
>
>I forgotten how much fun the Usenet thing can be.

     Maybe you should consider a conversation with colleagues a higher
priority than trolling.

Sincerely,

Gene Wirchenko