Misc/abrash-black-book
Watch
1
0
Fork
You've already forked abrash-black-book
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Deduped images

Browse source
This commit is contained in:
James Gregory 2013-12-30 12:25:34 +11:00
commit 9e52de9586
233 changed files with 128 additions and 128 deletions
Download patch file Download diff file Expand all files Collapse all files

2
01-01.html
View file

@ -53,7 +53,7 @@
<P>Notice that the above definition most emphatically does <I>not</I> say anything about making the software as fast as possible. It also does not say anything about using assembly language, or an optimizing compiler, or, for that matter, a compiler at all. It also doesn&#146;t say anything about how the code was designed and written. What it does say is that high-performance code shouldn&#146;t get in the user&#146;s way&#151;and that&#146;s <I>all</I>.</P>
<P>That&#146;s an important distinction, because all too many programmers think that assembly language, or the right compiler, or a particular high-level language, or a certain design approach is the answer to creating high-performance code. They&#146;re not, any more than choosing a certain set of tools is the key to building a house. You do indeed need tools to build a house, but any of many sets of tools will do. You also need a blueprint, an understanding of everything that goes into a house, and the ability to <I>use</I> the tools.</P>
<P>Likewise, high-performance programming requires a clear understanding of the purpose of the software being built, an overall program design, algorithms for implementing particular tasks, an understanding of what the computer can do and of what all relevant software is doing&#151;<I>and</I> solid programming skills, preferably using an optimizing compiler or assembly language. The optimization at the end is just the finishing touch, however.</P>
<TABLE WIDTH="100%"><TD WIDTH="5%" VALIGN="TOP"><IMG SRC="images/01-01i.jpg"><TD WIDTH="95%"><SMALL><I>Without good design, good algorithms, and complete understanding of the program&#146;s operation, your carefully optimized code will amount to one of mankind&#146;s least fruitful creations&#151;a fast slow program</I>.</SMALL>
<TABLE WIDTH="100%"><TD WIDTH="5%" VALIGN="TOP"><IMG SRC="images/i.jpg"><TD WIDTH="95%"><SMALL><I>Without good design, good algorithms, and complete understanding of the program&#146;s operation, your carefully optimized code will amount to one of mankind&#146;s least fruitful creations&#151;a fast slow program</I>.</SMALL>
</TABLE>
<P>&#147;What&#146;s a fast slow program?&#148; you ask. That&#146;s a good question, and a brief (true) story is perhaps the best answer.
</P>