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

Use proper lists instead of DLs with bullet points

Browse source
This commit is contained in:
James Gregory 2013-12-30 13:34:37 +11:00
commit 7e957c0bb4
12 changed files with 83 additions and 83 deletions
Download patch file Download diff file Expand all files Collapse all files

18
01-02.html
View file

@ -39,15 +39,15 @@
<H3><A NAME="Heading5"></A><FONT COLOR="#000077">Rules for Building High-Performance Code</FONT></H3>
<P>We&rsquo;ve got the following rules for creating high-performance software:
</P>
<DL>
<DD><B>&#149;</B>&nbsp;&nbsp;Know where you&rsquo;re going (understand the objective of the software).
<DD><B>&#149;</B>&nbsp;&nbsp;Make a big map (have an overall program design firmly in mind, so the various parts of the program and the data structures work well together).
<DD><B>&#149;</B>&nbsp;&nbsp;Make lots of little maps (design an algorithm for each separate part of the overall design).
<DD><B>&#149;</B>&nbsp;&nbsp;Know the territory (understand exactly how the computer carries out each task).
<DD><B>&#149;</B>&nbsp;&nbsp;Know when it matters (identify the portions of your programs where performance matters, and don&rsquo;t waste your time optimizing the rest).
<DD><B>&#149;</B>&nbsp;&nbsp;Always consider the alternatives (don&rsquo;t get stuck on a single approach; odds are there&rsquo;s a better way, if you&rsquo;re clever and inventive enough).
<DD><B>&#149;</B>&nbsp;&nbsp;Know how to turn on the juice (optimize the code as best you know how when it <I>does</I> matter).
</DL>
<ul>
<li>Know where you&rsquo;re going (understand the objective of the software).</li>
<li>Make a big map (have an overall program design firmly in mind, so the various parts of the program and the data structures work well together).</li>
<li>Make lots of little maps (design an algorithm for each separate part of the overall design).</li>
<li>Know the territory (understand exactly how the computer carries out each task).</li>
<li>Know when it matters (identify the portions of your programs where performance matters, and don&rsquo;t waste your time optimizing the rest).</li>
<li>Always consider the alternatives (don&rsquo;t get stuck on a single approach; odds are there&rsquo;s a better way, if you&rsquo;re clever and inventive enough).</li>
<li>Know how to turn on the juice (optimize the code as best you know how when it <I>does</I> matter).</li>
</ul>
<P>Making rules is easy; the hard part is figuring out how to apply them in the real world. For my money, examining some actual working code is always a good way to get a handle on programming concepts, so let&rsquo;s look at some of the performance rules in action.
</P>
<H4 ALIGN="LEFT"><A NAME="Heading6"></A><FONT COLOR="#000077">Know Where You&rsquo;re Going</FONT></H4>