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 markdown style lists

Browse source
This commit is contained in:
James Gregory 2013-12-31 07:31:51 +11:00
commit 307b59584f
17 changed files with 120 additions and 120 deletions
Download patch file Download diff file Expand all files Collapse all files

14
01-02.md
View file

@ -14,20 +14,20 @@ pages: 007-009
We've got the following rules for creating high-performance software:
- Know where you're going (understand the objective of the software).
- Make a big map (have an overall program design firmly in mind, so
* Know where you're going (understand the objective of the software).
* 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).
- Make lots of little maps (design an algorithm for each separate part
* Make lots of little maps (design an algorithm for each separate part
of the overall design).
- Know the territory (understand exactly how the computer carries out
* Know the territory (understand exactly how the computer carries out
each task).
- Know when it matters (identify the portions of your programs where
* Know when it matters (identify the portions of your programs where
performance matters, and don't waste your time optimizing the rest).
- Always consider the alternatives (don't get stuck on a single
* Always consider the alternatives (don't get stuck on a single
approach; odds are there's a better way, if you're clever and
inventive enough).
- Know how to turn on the juice (optimize the code as best you know
* Know how to turn on the juice (optimize the code as best you know
how when it *does* matter).
Making rules is easy; the hard part is figuring out how to apply them in