Article View: comp.specification
Article #64Re: formal methods in US
From: Andrew Walduck
Date: Tue, 14 Apr 1992 05:09
Date: Tue, 14 Apr 1992 05:09
51 lines
2901 bytes
2901 bytes
In article <4521577@harvee.UUCP>, esj@harvee.UUCP (Eric S Johansson) writes:
|> In article <1992Mar31.164952.18327@beaver.cs.washington.edu>
jon@cs.washington.edu
|> (Jon Jacky) writes:
|>
|> > In article <1992Mar31.015456.2392@oracorp.com> narayana@oracorp.com
(K. T. Narayana) writes:
|> > > I would appreciate if people cut off this half baked survey of people
|> > > working in formal methods in north america.
|> > > ...kt
|> >
|> > In contrast, I would like to say that I have found this interesting
and do
|> > appreciate seeing it, and would welcome additional contributions.
It's easy
|> > enough for people to skip over articles that do not interest them.
|>
|>
|> I too have found this communication interesting and I have been
|> entertaining thoughts of it degenerating into a comp.specification.aa
|> meeting (my name is eric and I am a coder :-)
|>
|> This discussion is dealing (indirectly) with change. How do I get {
|> myself, my manager, my coworkers, ... } to change to understand and
|> hopefully use formal methods. by understanding what we learn, how we
|> learn it and what motavates us to learn formal methods, we can convince
|> others and know what to teach them. In trying to change my work environment
|> I have encountered indifference, hostility, fear and far too little
|> excitement.
How do you get people to use assert() {a form of
pre-conditions/post-conditions}
How do you get people to design instead of hack??
How do you get people to "throw the first 2 away"??
How do you explain to people that code is "written once" ... "maintained
forever"
How do you explain to people that finding bugs is a "good thing"... as it
means you won't ship them to the customer...
How do you get people to re-use?? Not re-invent??
Nobody likes to be told how to do their job. Or that they could do it better...
or that there is a better way...
This is more of a social problem...a resistance to new ideas...
(the solution to which has been left as an excercise for the student!! ;-)
Andrew Walduck -- OMRON Japan -- andrew@lsa.ncl.omron.co.jp
-------------------------------------------------------------------------------
Henry Spencer says "Retch barf."
-------------------------------------------------------------------------------
Technical Details
Message-ID:
<1411@frf.omron.co.jp>Path:
arc1-ca.pugleaf.net!sparky!uunet!sun-barr!sh.wide!astemgw!relay-omron!frf!lsa.ncl.omron.co.jp!andrewReferences:
<1992Mar29.180106.3876@gmuvax2.gmu.edu> <1992Mar31.015456.2392@oracorp.com> <1992Mar31.164952.18327@beaver.cs.washington.edu> <4521577@harvee.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!sun-barr!sh.wide!astemgw!relay-omron!frf!lsa.ncl.omron.co.jp!andrew From: andrew@lsa.ncl.omron.co.jp (Andrew Walduck) Newsgroups: comp.specification Subject: Re: formal methods in US Message-ID: <1411@frf.omron.co.jp> Date: 14 Apr 92 05:09:36 GMT References: <1992Mar29.180106.3876@gmuvax2.gmu.edu> <1992Mar31.015456.2392@oracorp.com> <1992Mar31.164952.18327@beaver.cs.washington.edu> <4521577@harvee.UUCP> Sender: news@frf.omron.co.jp Reply-To: andrew@lsa.ncl.omron.co.jp (Andrew Walduck) Distribution: comp.specification Lines: 51