|
Fred, I couldn't agree with you more. To attempt to implement the true OO philosophies on a first project is almost certainly to court disaster. I know, I tried a few years ago when I was first learning Java. I figured my extensive knowledge in applications and programming would be enough to be able to implement the "simple" concepts of OO. I saved some of that code. Just to pull out and look at once in a while. It's humbling. <grin> Instead, I've learned that you should write code. It doesn't hurt to have some knowledge of OO concepts, even cursory, because you may get ideas as you're writing, but it's far more important to just start writing. Then, sit back and look at what you've done, and see where things can be improved. The philosophy I espoused earlier - find the commonalities and abstract them, find the differences and parameterize them - will go a long way towards giving you better code. Then, as your code base gets larger, you'll start seeing the patterns form, almost of themselves, as you continue to tweak your code. I've learned one thing, though, which goes along with Larry's assertion that "lots of parameters means the design is probably incorrect". Joe's Java Axiom #1 is that you know you're getting close to a good design when you start REMOVING code when you're adding new features. Joe > -----Original Message----- > From: owner-java400-l@midrange.com > [mailto:owner-java400-l@midrange.com]On Behalf Of Fred Kulack > Sent: Wednesday, March 14, 2001 12:18 PM > To: JAVA400-L@midrange.com > Subject: RE: HTML to XML, vice versa > > > > I guess the only thing I would add is that discussions like this > tend to be too theoretical/academic and lead DIRECTLY to > the large cost that you were talking about earlier. > I find that these academic discussions rarely tend to > optimize my development. > > They ARE good to have, they're fun, and they lubricate my brain, > to let details slip in more easily, but what you really > need to do is finish this piece of code exactly as YOU THINK > it should be done and run with it for a while. > > Then: > change it, realizing that the OO model is not quite correct, > rewrite it and run with it for a while. > > Repeat this a couple of times until you get it correct. > > I.e. ignore us all except for any fun and eduction, gleaning > bits of information from the conversation. > > The first 'n' OO projects will consist of MASSIVE > rewrites on a large scale. Don't worry, you'll get better. > > Let experience with your real code (possibly saving old > incantations of it for reference) be your final guide. > > Keep up the discussion though. 8-) > > > "The stuff we call "software" is not like anything that human society > is used to thinking about. Software is something like a machine, and > something like mathematics, and something like language, and > something like thought, and art, and information... > but software is not in fact any of those other things." > Bruce Sterling - The Hacker Crackdown > > Fred A. Kulack - AS/400e Java and Java DB2 access, Jdbc, JTA, etc... > IBM in Rochester, MN (Phone: 507.253.5982 T/L 553-5982) > mailto:kulack@us.ibm.com Personal: mailto:kulack@bresnanlink.net > AOL Instant Messenger: Home:FKulack Work:FKulackWrk > > +--- > | This is the JAVA/400 Mailing List! > | To submit a new message, send your mail to JAVA400-L@midrange.com. > | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. > | To unsubscribe from this list send email to > JAVA400-L-UNSUB@midrange.com. > | Questions should be directed to the list owner: joe@zappie.net > +--- > +--- | This is the JAVA/400 Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner: joe@zappie.net +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.