Re: Re: Ada Professional Questions

Re: Re: Ada Professional Questions

[Dan Kary]

Tony Alden writes:
> This is a very snobbish set of questions...
> I call your set of questions snobbish because you are implying that Ada is
> some how above other programming languages.

I've read Ed Berard's article several times now and I simply do not see this
implication.  I do see the implication that Ada is *different* from other
languages.  If we were talking about spoken languages, distinguishing a 
translator who spoke English and French from one who spoke English and German,
(but could learn French real soon) would imply a difference that is meaningful
to someone searching for English to French translation without berating the
English to German translator.  I think this is a fair comparison, it takes
time to gain fluency in a new programming language.

> The major point is that if someone codes a program in Ada and the program is
> sound (i.e. works well), and organized accourding to the packaging constructs
> supplied by Ada then no one should have any complaints.

The major point of developing and enforcing the use of Ada is to get control
of the software crisis DoD is experiencing.  DoD systems tend to be long lived,
fifteen years is common.  Of course it has to work well, more importantly it
has to be maintainable.  Original development is a small part of the life cycle
cost of a system, maintenance is the reason the software crisis exists.  A
developer who is struggling to learn the language while struggling to develop
the application is at a severe disadvantage to the developer who already knows
the language.

If I were searching for an organization to port UNIX to my new processor and
had a choice between a respectable, established DP shop that specialized in
COBOL applications and a startup that employed C programmers recently graduated
from Berkeley (or NDSU), my choice would not indicate that I thought COBOL
programmers were a lower form of life or generally less capable individuals.
My choice would reflect the fact that I understand the importance of experience
with the language in question.

Returning to the maintainability issue, I would like to ask a fourth question.

    4) From a contracting office's point-of-view: How does one specify
       maintainability criteria for acceptance.  Obviously a program that
       does not work would be rejected, why should a program that is 
       expensive to maintain be accepted?

> In summary, your questions suggest that the average programmer is 
> incapable of learning Ada but somehow capable of learning say Pascal.

Again, I see no such implication.  I see (and agree with) an implication that
someone who is fluent with a given language has an advantage over someone who
has never used the language.  I take a generic view of this list of questions.
Substitute 'FORTRAN' or 'C' or whatever you want for 'Ada' in the list and it
is equally valid.  If a specific programming language or operating system is
required for implementation of a given system (for whatever reason), then
competence with that system is an important issue.

I am most interested in answers to question three:

>  Am I improving, or getting worse?

No matter what language a group is using, habits will develop.  What will be the
end effect of these habits?  Are we digging ourselves into a deeper and deeper
rut?  How do we know before it's too late?

> You really show examine the motivations of you questions before you put
> them out for public response.  

Pure as the driven snow.  (I see *lots* of driven snow in Fargo, ND)

Dan Kary
North Dakota State University
Computer Science Department
300 Minard Hall
Fargo, ND   58105
(701) 237-8171
ihnp4!dicomed!nckary