• To: "'Lou Munajim'" <louai@b...>, Jeff Lowery <Jeff.Lowery@c...>, "'Uche Ogbuji'" <uche.ogbuji@f...>, Jonathan Robie <jonathan.robie@d...>
• Subject: RE: Design as, one hopes, not premature optimization
• From: Jeff Lowery <Jeff.Lowery@c...>
• Date: Wed, 2 Apr 2003 17:51:16 -0800
• Cc: Chiusano Joseph <chiusano_joseph@b...>, xml-dev@l...

> >
> > I believe implementation is the last step of design, and 
> optimization
> comes
> > after that.
> >
> 
> There are two types of optimizations that can occur here.

[snipping the good stuff...]

I was being just _teensy_ bit tongue-in-cheek.  

Implementation is a kind of formal proof of a design.  Once the holes in the
original design are encountered in the implementation attempt and patched
over, optimization is by then generally less important than shipping the
@#!$ thing, so that gets done in the next release.  

Maybe it's just me...

• Prev by Date: Re: Design as, one hopes, not premature optimization
• Next by Date: Re: CDATA
• Previous by thread: Re: On the aparent importance of emoticons (was "Designas, one hopes, not premature optimization")
• Next by thread: Turning Off the Output Stream or Just a Return Value from a Template
• Index(es):
  • Date
  • Thread