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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 107f24,582dff0b3f065a52 X-Google-Attributes: gid107f24,public X-Google-Thread: 1014db,582dff0b3f065a52 X-Google-Attributes: gid1014db,public X-Google-Thread: 103376,bc1361a952ec75ca X-Google-Attributes: gid103376,public X-Google-Thread: 109fba,582dff0b3f065a52 X-Google-Attributes: gid109fba,public X-Google-ArrivalTime: 2001-08-06 08:42:41 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!news.ems.psu.edu!not-for-mail From: cross@augusta.math.psu.edu (Dan Cross) Newsgroups: comp.lang.ada,comp.lang.c,comp.lang.c++,comp.lang.functional Subject: Re: How Ada could have prevented the Red Code distributed denial of service attack. Date: 6 Aug 2001 11:42:39 -0400 Organization: Mememememememmeme Message-ID: <9kmdtf$r8j@augusta.math.psu.edu> References: <3b6e4ab8.1457529830@news.worldonline.nl> <9km99q$qt3@augusta.math.psu.edu> <3b6ea1c1.1479814516@news.worldonline.nl> NNTP-Posting-Host: augusta.math.psu.edu X-Trace: boatanchor.ems.psu.edu 997112561 9625 146.186.132.2 (6 Aug 2001 15:42:41 GMT) X-Complaints-To: security@psu.edu NNTP-Posting-Date: 6 Aug 2001 15:42:41 GMT Xref: archiver1.google.com comp.lang.ada:11379 comp.lang.c:72471 comp.lang.c++:80334 comp.lang.functional:7348 Date: 2001-08-06T15:42:41+00:00 List-Id: In article <3b6ea1c1.1479814516@news.worldonline.nl>, Richard Bos wrote: >> >> Huh? ``Design as you go'' is rarely a good strategy; you should always >> >> have some idea how to start before applying fingers to keyboard. >> > >> >Since when does programming start with applying fingers to keyboard? >> >> These days, most of the time. :-) But then, that's my point; it's a bad >> idea. > >Well, then, what's your point in contrasting "programming defects" with >"design defects"? ``Programming,'' to me, means the ``act of programming.'' This involves thinking and typing, mostly. The software development process involves a lot more than just programming, including, but not limited to, requirements gathering and analysis, design, and testing. When you say ``programming,'' you lead me to believe you are refering to the act of writing code, overall, a very small part of the over all process. But, these aren't just my terms, they're industry standard with slight variances in nomenclature (requirements ellicitation versus gathering, and so forth). Anyway, as regards your question: I drew a distinction to highlight the fact that mistakes can be made at very stages and levels of the software development process. Sometimes, they happen in the design of the system, sometimes in the implementation or actual programming. Unfortunately, these days, a lot of programs just look like random typing. The programmer won't even make an effort to keep his or her software tidy looking. - Dan C.