Xref: utzoo comp.lang.c:27159 comp.lang.misc:4620
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!uunet!mcsun!hp4nl!targon!ruud
From: ruud@targon.UUCP (Ruud Harmsen)
Newsgroups: comp.lang.c,comp.lang.misc
Subject: Re: A note for those not consumed by efficiency worries
Message-ID: <1084@targon.UUCP>
Date: 23 Mar 90 12:54:56 GMT
References: <1990Mar21.061420.9862@athena.mit.edu> <1990Mar21.163413.10711@aqdata.uucp> <1990Mar22.072712.10902@diku.dk>
Reply-To: ruud@targon.UUCP (Ruud Harmsen)
Organization: Nixdorf Computer BV., SWP, P.O. Box 29,Vianen, The Netherlands
Lines: 16

In article <1990Mar22.072712.10902@diku.dk> jensting@skinfaxe.diku.dk (Jens Tingleff) writes:
>
>	MAKE THE THING WORK, THEN MAKE IT FAST.
>
True.  But only with one very important footnote:

While making the thing just work, do consider performance, and know where and
how you might want to optimise later.
If in the design of a programme or system you totally disregard all
performance issues, you might have to rebuild large parts from scratch,
and/or make the whole thing totally incomprehensible when optimisizing.

I've seen things like that happen, and I can tell you it's a tragic sight
to watch.  A much better approach is to have the spots for optimization
marked and planned, so it is easy to fulfill, will be really effective
and does not violate the original design.