From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,4b06f8f15f01a568 X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: Why C++ is successful Date: 1998/08/14 Message-ID: #1/1 X-Deja-AN: 381008438 References: <6qg3on$kjq$2@reader1.reader.news.ozemail.net> <6qrdn4$4ac@drn.newsguy.com> X-Complaints-To: usenet@news.nyu.edu X-Trace: news.nyu.edu 903074156 16374 (None) 128.122.140.58 Organization: New York University Newsgroups: comp.lang.ada Date: 1998-08-14T00:00:00+00:00 List-Id: Someone with no particular name replied to me: <<>An amazing number of programmers these days work by writing approximate junk >code, and then spend amazing amounts of time trying to bash the code into >shape using a debugger. > soory, but this is called meeting the big boss deadline. it is very frequent occurance in the modern to post-modern computing information systems age. got'a get that code out of the door fast, else the competition will do it first! >> On the contrary! The approach of bashing things into shape with a debugger is incredibly inefficient. You can only afford it if you do NOT have tight deadlines. If you have tight deadlines, then it becomes absolutely crucial to avoid premature coding, and to write things right the first time, because there is not enough time for inefficient fiddling around.