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: 103376,d89b08801f2aacae X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-05-07 08:28:08 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed1.cidera.com!Cidera!cyclone.socal.rr.com!cyclone3.kc.rr.com!news3.kc.rr.com!twister.socal.rr.com.POSTED!not-for-mail Message-ID: <3CD7F29C.196F8D20@san.rr.com> From: Darren New X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Is strong typing worth the cost? References: <4519e058.0204290722.2189008@posting.google.com> <3CCE8523.6F2E721C@earthlink.net> <3CCEB246.9090009@worldnet.att.net> <3CCFD76A.A60BB9A8@flash.net> <3CD0A3B8.7B7C8622@san.rr.com> <3CD15FAE.6DEE0AD@despammed.com> <3CD16B60.93078396@san.rr.com> <3CD1B496.DBE8ADC4@san.rr.com> <3CD1DE85.C00AD2A9@san.rr.com> <3CD329FE.C067B6CE@san.rr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 07 May 2002 15:28:07 GMT NNTP-Posting-Host: 66.75.151.160 X-Complaints-To: abuse@rr.com X-Trace: twister.socal.rr.com 1020785287 66.75.151.160 (Tue, 07 May 2002 08:28:07 PDT) NNTP-Posting-Date: Tue, 07 May 2002 08:28:07 PDT Organization: RoadRunner - West Xref: archiver1.google.com comp.lang.ada:23651 Date: 2002-05-07T15:28:07+00:00 List-Id: Marin David Condic wrote: > > Maybe. Maybe not. I have not made a thorough study of it, but have read some > descriptions of it. But as for "Waterfall" - I don't think anybody ever > actually did anything of significance in a pure "Waterfall" method - even if > they say they did. Almost any project of size has to deal with changes > midstream that require going back to revisit requirements or design or other > things along the way - thus really creating a kind of spiral model. Most of > the projects I've been on have involved iterative builds of some sort - how > fast and when are always an issue. Sure. But by "waterfall" I mean the development model where first you talk to the customers and get all the requirements, then you plan how you're going to structure the code, then ..... In XP, if you can't implement it this week, it's not a requirement. You don't even consider it. It's off the scope. > Keep in mind that a lot of technologies have come out where adherents start > to think they have found a panacea - including Ada. Usually, you gain > something and give something else up along the way. Yep. I think there are a lot of situations where XP is not effective. Pair Programming is going to be very difficult if you don't have everyone in the same office. If you don't have a customer there to tell you the next set of requirements every day/week and to answer questions, it's likely not to work well. If the project is big enough that you need more than about a dozen programmers, I don't think it would work well. If it's a system where a language like Smalltalk isn't reasonable (say, embedded or real-time systems) it's not going to work. If it's a system where you aren't developing on the same class of machines that you're deploying on, it's not going to work well. I'm told that it works well for things like libraries and components for general distribution, but I don't really believe that, due to the customer not being there. Etc. I don't think it's a panacea at all. Perhaps some of the proponents do. Again, I only brought it up as an example of a situation in which strong typing *might* be more of a cost than a benefit. -- Darren New San Diego, CA, USA (PST). Cryptokeys on demand. The 90/10 rule of toothpaste: the last 10% of the tube lasts as long as the first 90%.