-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
uml is very effective for development in oop. its genius. If ure
developing oop based apps, theres no better way to develop the class
diagramm or the sequence diagramm. There are serveral tools for
drawing them and generate from this diagram working c++, java or c#
code. this is the most advantage, as head dev u can give the
structure of the program without knowing the target programming
language. If u have to documentate ur programs, theres no better way...
If ure a C-programmer, theres no need for uml...(:
Karl
On Aug 13, 2006, at 5:36 PM, Marco Peereboom wrote:
On Sun, Aug 13, 2006 at 12:11:52AM -0400, Nick Guenther wrote:
On 8/12/06, Lilo Stich <[EMAIL PROTECTED]> wrote:
Hi
Normally when I do some developement at work, at make a paper
model, if
needed, before I start coding, or at about the same time. The
model works
as
a guideline.
I have been reading about UML and model practises in general.
What do coding-people on this list think about UML and design
modelling?
UML is evil. I've had one brush with it and ran away. My instructor
intended to force UML on us but gave up when I pointed out to him
that
the only reasonably usable free UML kit lacked about half of the UML
types.
UML is retarded.
UML is for the managers. Really. UML is promoted as being a good way
to document programs, except it is _clearly_ designed specifically
for
the C++/Java model, and if you have a functioning team of programmers
who document using simple standard techniques there should never be a
need for UML. UML is maybe useful for those large companies which are
constantly having people quit on them or get shuffled around, or at
least that's the only Use Case (get it?) I can see.
UML is retarded.
That said, I agree that learning formal methods in any area can
increase you precision in general. It's exercise.
-Nick
Just don't do UML.
UML is retarded.
Working for a large company this was being forced down our throats as
"corporate policy". The reality was that code was written and
tested first and
then we made the interns make the UML map. It added weeks of work
and made
everybody's life miserable. Mgmt figured it out and they went like:
"please
don't tell anyone but keep doing whatever you are doing". We did
see one
positive thing coming from the UML exercise namely, job security,
because the
code was write only.
So I agree with Nick's sentiment, Just say no to UML!
iD8DBQFE319L7h0sIchkcqsRAuYGAJ97rBYtv/+MoAEYzKCNmB3XEPPEEQCggg8+
NpneLkSObUTLhZI+rcT2NUQ=
=Jpob
-----END PGP SIGNATURE-----
