on 1/7/02 5:41 PM, "Andrew C. Oliver" <[EMAIL PROTECTED]> wrote:
> When I was much younger I used to go on BBSes and post "Which is better > Amiga or IBM?" and "Why not just use a Mac?" to see the fires rage. As > I grew up I found more productive ways to spend my time. Code > formatting is subjective. Your way is wrong and mine is right etc etc. > There are no conclusions to these arguments and have you perfected the > things that can be perfected to such a degree that you're ready to > tackle this one? I'm not talking about source code formatting, I'm talking about the issues surrounding making decisions, documenting those decisions and actually enforcing those decisions. The source code formatting is just a simple example of the failure. There are more. A good one that Sam worked on resolving fairly successfully is the one about Gump. Another issue which I see as a failure is the failure of projects to communicate with each other. > I would suggest there be one and only one stead-fast dead on code > standard. All public methods must provide javadoc siting the purpose of > the method. Get there first then worry about "_variables". THAT ISN'T THE ISSUE. -jon -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
