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: fac41,c7b637f8b783b7c X-Google-Attributes: gidfac41,public X-Google-Thread: f43e6,c7b637f8b783b7c X-Google-Attributes: gidf43e6,public X-Google-Thread: 109fba,c7b637f8b783b7c X-Google-Attributes: gid109fba,public X-Google-Thread: 103376,c7b637f8b783b7c X-Google-Attributes: gid103376,public X-Google-Thread: 1108a1,c7b637f8b783b7c X-Google-Attributes: gid1108a1,public X-Google-Thread: 107d55,c7b637f8b783b7c X-Google-Attributes: gid107d55,public From: doylep@ecf.toronto.edu (Patrick Doyle) Subject: Re: The great Java showcase (re: 2nd historic mistake) Date: 1997/08/30 Message-ID: #1/1 X-Deja-AN: 269070865 Sender: news@ecf.toronto.edu (News Administrator) References: <34023FC9.59E2B600@eiffel.com> X-Nntp-Posting-Host: skule.ecf Organization: University of Toronto, Engineering Computing Facility Newsgroups: comp.object,comp.software-eng,comp.lang.ada,comp.lang.eiffel,comp.lang.java.tech,comp.lang.c++ Date: 1997-08-30T00:00:00+00:00 List-Id: In article , Robert Dewar wrote: >Patrick said > ><spent looking for memory allocation bugs in C++. > > If this isn't the case with you then, well, I suppose you're >just the greatest darn programmer in the whole world.>> > > >Well different people have different styles in programming. I personally >like programming, but hate debugging, so I perfer to spend my effort >getting this right to start with. But I realize others prefer to spend >their time debugging -- it's a matter of taste partly -- although I >suspect that a lot of people do spend far too much time with a debugger. Hey, I don't like debugging either... >You do NOT have to be the "greatest darn programmer in the whole world" to >avoid wasting 40-50% of your time looking for memory allocation bugs in >C++, you just need to create the proper abstractoins in the first place. I'd love to know how. Do you have any references to techniques for this sort of thing? >Now to be fair, you may well be spending this time on other people's >poorly written code, in which case the blame lies elsewhere. Actually, in my case, that's true. In fact, for the bulk of my professional career, I've been upgrading legacy code, and I don't really know much else, so maybe I'm overestimating my problems with memory. >But if you think my comment is a cheap shot, then you are far from being >sufficiently aware of what can be achieved by proper software process, >and this does NOT require super duper clever programmers, it is something >that can be achieved by good management, and good choice of techniques, >languages, and tools, with typical competent programmers, not super stars. Sure, but I still think it was a cheap shot. Someone said "I spend X amount of time finding memory bugs" and you said "then you must be doing something terribly wrong". Now that you've explained your reasoning, I think we're all better off. -PD -- -- Patrick Doyle doylep@ecf.utoronto.ca