🚀 go-pugleaf

mfeldman@seas.gwu.edu (Michael Feldman) wrote:
>(I)   It's easier to make a correct program fast than a fast program correct;
>(II)  Fast enough is fast enough;
>(III) If you've _measured_ it and it isn't fast enough, do what you have
>      to do to get the performance up;
>(IV)  90% of the work is done by 10% of the code, so don't bother
>      optimizing the other 90% of the code.

Unfortunately, many people believe that
(I)   It's easier to make a correct program fast than a fast program correct;
      but the latter is what I have to do.
(II)  There's no such thing as fast enough;
(III) If your job description includes the words "real-time" do anything
      you feel like to get the performance up--especially
(IV)  turn off the optimizer and butcher^H^H^H^H^H^H^Hoptimize the code
      until it screams.