SJS wrote:
When I've been on teams that did that, the result was a truly terrible
design. Of course, heavy use of UML may have contributed to that as
well.
There's a difference between writing the documentation and trying to
implement the code in a non-coding language. There's really only so much
meta you need.
If you write a word processor without knowing what kind of formatting
you want to be able to do, it's going to be a mess internally and
unusable externally.
Sounds like you're solving problems that you already know how to solve.
*My* take is that you have to know what problem you're going to solve,
and approximately how you'll approach it, before you can write usable
code. If you start coding before you know what you're supposed to do,
*and* you keep that version of the code, it's going to be very messy
very quickly.
--
Darren New / San Diego, CA, USA (PST)
"That's pretty. Where's that?"
"It's the Age of Channelwood."
"We should go there on vacation some time."
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
