[
Lists Home |
Date Index |
Thread Index
]
> > > the accepted wisdom that premature optimization is evil?
>
> Don't fall into the trap of reading this as "early optimization is
> evil", let alone "you can ignore performance during the design stage".
<SIGH/>
I used to refuse to use emoticons. I always figured that ":-)" was nothing
more than an ironical amplifier to anything from which the reader might take
offense, and that it also had about the same effect on a good joke as an
unnecessary laugh track.
But everytime I try posting a joke without an emoticon, the above happens.
I guess there's an unfortunate lesson...?
--
Uche Ogbuji Fourthought, Inc.
http://uche.ogbuji.net http://4Suite.org http://fourthought.com
Use internal references in XML vocabularies - http://www-106.ibm.com/developerw
orks/xml/library/x-tipvocab.html
Universal Business Language (UBL) - http://www-106.ibm.com/developerworks/xml/l
ibrary/x-think16.html
EXSLT by example - http://www-106.ibm.com/developerworks/library/x-exslt.html
The worry about program wizards - http://www.adtmag.com/article.asp?id=7238
Use rdf:about and rdf:ID effectively in RDF/XML - http://www-106.ibm.com/develo
perworks/xml/library/x-tiprdfai.html
Keep context straight in XSLT - http://www-106.ibm.com/developerworks/xml/libra
ry/x-tipcurrent.html
Using SAX for Proper XML Output - http://www.xml.com/pub/a/2003/03/12/py-xml.ht
ml
SAX filters for flexible processing - http://www-106.ibm.com/developerworks/xml
/library/x-tipsaxflex.html
|
