TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy


Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: "Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
From: Jacob Sparre Andersen <[log in to unmask]>
Date: Mon, 26 Feb 2001 17:58:09 +0100
In-Reply-To: <[log in to unmask]>
MIME-Version: 1.0
Reply-To: Jacob Sparre Andersen <[log in to unmask]>
Parts/Attachments: TEXT/PLAIN (36 lines)

> Thus in one statement making my assertion that this is
> not a language issue, but a cultural one.

I think you are right.

As a friend of mine once said about the output from Aonix'
Ada-to-C compiler:

   It is probably better than C code written by C
   programmers, but it is definitely worse than C
   code written by Ada programmers.

> I would bet that the average person on this list
> actually has oil changes when they are suggested 8).

Uhmmm. I haven't sprayed the chain on my bike in a month.

> I have found that if you produce an GUI executable that
> 'dances' early, the scrutiny about your ability to
> finish quickly is removed.

Yes. But at the same time, it builds an expectation that you
almost have finished the system. I have simply stopped
showing "live" GUI prototypes and use a hand-drawn
paper-based GUI for presentations until the system is close
to be useable. - A strategy I am afraid only is practical
for the development of smaller systems.

"There are only two types of data:
                         Data which has been backed up
                         Data which has not been lost - yet"