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=-0.4 required=5.0 tests=AC_FROM_MANY_DOTS,BAYES_00 autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,41100a78496a4c71 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-04-05 17:38:39 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!lon1-news.nildram.net!154.32.99.10.MISMATCH!psiuk-p2!psiuk-p3!uknet!psiuk-n!news.pace.co.uk!nh.pace.co.uk!not-for-mail From: "Marin David Condic" Newsgroups: comp.lang.ada Subject: Re: Nethack! (was): AdaGames Date: Fri, 5 Apr 2002 09:51:25 -0500 Organization: Posted on a server owned by Pace Micro Technology plc Message-ID: References: <98104da8.0203280310.143a1c18@posting.google.com> <4519e058.0203290613.73b55af4@posting.google.com> <6g4gaugv9a85i56kvgcgmu4h2jkjprutec@4ax.com> <4519e058.0204010704.ed2cd06@posting.google.com> <4519e058.0204021030.14127b06@posting.google.com> <4519e058.0204030750.78a30287@posting.google.com> <3CAC7AC6.A6DBDC32@despammed.com> <4519e058.0204050643.30f2e516@posting.google.com> NNTP-Posting-Host: dhcp-200-133.miami.pace.co.uk X-Trace: nh.pace.co.uk 1018018286 7004 136.170.200.133 (5 Apr 2002 14:51:26 GMT) X-Complaints-To: newsmaster@news.cam.pace.co.uk NNTP-Posting-Date: 5 Apr 2002 14:51:26 GMT X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Xref: archiver1.google.com comp.lang.ada:22171 Date: 2002-04-05T14:51:26+00:00 List-Id: "Ted Dennison" wrote in message news:4519e058.0204050643.30f2e516@posting.google.com... > > Then there was the week I decided to refactor several badly designed > units, and got a visit from a bemused team lead mock-castigating me > for making *negative* progress that week. :-) > > Another Helpful Household Hint is to always insert spurious delay statements in any new body of code. That way, when your users start complaining about the performance that is beyond your control, you can at least immediately take out the delay statements and say "Well I got you a 25% improvement with some quick code changes - be patient and I'll keep working on the harder problems..." Then, of course, you do nothing and wait for the next generation of hardware to come along and fix your problems for you. :-) MDC -- Marin David Condic Senior Software Engineer Pace Micro Technology Americas www.pacemicro.com Enabling the digital revolution e-Mail: marin.condic@pacemicro.com