Re: Do C++ and Java professionals use UML??

From: "John B. Matthews" <john.b..matthews@1:261/38.remove-k2r-this>

From: "John B. Matthews" <john.b..matthews@1:261/38.remove-qhs-this>

From: "John B. Matthews" <john.b..matthews@1:261/38.remove-p82-this>

From: "John B. Matthews" <nospam@nospam.invalid>

In article <R9udnfv4C4qtCYPNnZ2dnUVZ_rednZ2d@earthlink.com> ,
Patricia Shanahan <pats@acm.org> wrote:

[...]
> >> There are indeed some things that are really necessary for
> >> effective use of a given tool. I put the sharp end of my chisel
> >> against the wood, and tap the blunt end with a mallet. I'm sure
> >> everyone using a wood chisel and a mallet does that the same way
> >> round.
> >
> > One sharp on both ends might be widely rejected as dangerous; one
> > blunt on both ends might be an unfamiliar style of draw knife. I
> > see no harm in polite explication in either case.
> >
> >> The analogy for the situation that started this sub-thread is as
> >> though the excavator were delivered with green paint, and most
> >> excavators of that model were painted green. A particular user has
> >> a lot of hole-related tools such as pile drivers and other models
> >> of excavators, and choose to paint all of them blue to avoid the
> >> inconvenience of keeping different paint colors around.
> >>
> >> He asked a question about lubricating the excavator, but some
> >> people take one look at a photo of his blue excavator and tell him
> >> that it should be green, that he will never be a capable excavator
> >> user unless he paints it green, and that green paint is the
> >> excavator way.
> >
> > A medical supply vendor asks for help marketing a new line of
> > compressed nitrous oxide. Instead of the familiar blue, the tanks
> > are green, "nitrous" is almost illegible, and "oxide" is misspelled
> > in a particularly unfortunate way. No one comments. An errant
> > bottle finds its way to a matching green oxygen manifold; hapless
> > victims enter a persistent vegetative state. Misery ensues.
>
> This seems like a good argument in support of sticking to one style,
> regardless of brand. The programming equivalent is using one set of
> conventions for indentation and identifier construction regardless of
> programming language. That way, there is less risk of someone
> misreading an identifier because it is in a different style from code
> in another language they have been using.

Sorry, the best I can muster is a few variations per language. I've grown too
dependent on perceptual cues that help me change gear into whatever language I
face. This may be an artifact of having worked largely in code bases that
already followed established, widely used guidelines.

--
John B. Matthews
trashgod at gmail dot com
<http://sites.google.com/site/drjohnbmatthews>

-+- BBBS/Li6 v4.10 Dada-1
+ Origin: Prism bbs (1:261/38)
-+- Synchronet 3.16a-Win32 NewsLink 1.98
Time Warp of the Future BBS - telnet://time.synchro.net:24

-+- BBBS/Li6 v4.10 Dada-1
+ Origin: Prism bbs (1:261/38)
-+- Synchronet 3.16a-Win32 NewsLink 1.98
Time Warp of the Future BBS - telnet://time.synchro.net:24

-+- BBBS/Li6 v4.10 Dada-1
+ Origin: Prism bbs (1:261/38)
-+- Synchronet 3.16a-Win32 NewsLink 1.98
Time Warp of the Future BBS - telnet://time.synchro.net:24

--- BBBS/Li6 v4.10 Dada-1
* Origin: Prism bbs (1:261/38)
--- Synchronet 3.16a-Win32 NewsLink 1.98
Time Warp of the Future BBS - telnet://time.synchro.net:24