• From: Ihe Onwuka <ihe.onwuka@g...>
• To: Rick Jelliffe <rjelliffe@a...>
• Date: Thu, 21 Nov 2013 08:51:32 +0000

On Thu, Nov 21, 2013 at 2:18 AM, Rick Jelliffe <rjelliffe@a...> wrote:
> Knuth was wrong about avoiding premature optimization. Because there is now
> a generation of coders who take him to mean that you should initially ignore
> performance or implementation heuristics or real-time aspects and
> concentrate on correctness. The result is systems that fall over in
> certification or integration testing.
>

Actually one can concretize this principle with your everyday XSLT
transformation.

How many times have you combined a bunch of patterns into a single
template rule by unionising the match attribute (premature
rationalisation) only to subsequently find there is actually some
nuance that doesn't apply to one or more of  the patterns you
combined?

Never. None.

Hmmm must be just me then.

• References:
  • How to design XML to have broad utility and yet also enableefficient application processing?
    • From: "Costello, Roger L." <costello@m...>
  • Re: How to design XML to have broad utility and yet alsoenable efficient application processing?
    • From: Peter Hunsberger <peter.hunsberger@g...>
  • RE: How to design XML to have broad utility and yet alsoenable efficient application processing?
    • From: David Lee <dlee@c...>
  • Re: How to design XML to have broad utility and yet alsoenable efficient application processing?
    • From: Peter Hunsberger <peter.hunsberger@g...>
  • Re: How to design XML to have broad utility and yet alsoenable efficient application processing?
    • From: Rick Jelliffe <rjelliffe@a...>
  • Re: How to design XML to have broad utility and yet alsoenable efficient application processing?
    • From: Peter Hunsberger <peter.hunsberger@g...>
  • Re: How to design XML to have broad utility and yet alsoenable efficient application processing?
    • From: Rick Jelliffe <rjelliffe@a...>