-
The chapter on tuning requires heavy technical review. It is largely synthesized from recommendations by others, but needs to be buttoned up and fact-checked.
-
The technical chapters and the "Mu" chapters will be interleaved later, but they’re held separate for now.
-
check for consistent usage:
-
"hash" (always means "dictionary"), vs "digest" (always means "MD5 or whatever")
-
whatever replaces merge/shuffle/sort in reduce steps
-
"pivot", not "reshape"
-
<remark>JOEMAN:Comment Consider forming this into a more clear question. The analysis that proceeds is of course interesting, but you don’t stage me with a very clear question. Seeking the 'flavor' of a region doesn’t immediately strike me as a problem I have or can imagine having - unless I’m trying to create a Lonely Planet guide, for example. More context for the example can encourage interest and attention.</remark>
There’s actually a direct version of this: early Computers, i.e. people with the job title Computer
-
explain more of the role of chimp and elephant, slightly tighter links
Choose a different word for "locality" — "pivot"
Make the locality examples either longer, or shorter — but mostly clearer.
-
Link-shorten links
-
For large export images: http://zoom.it/pages/about/
-
Does a bulleted list have a period at the end of the line?
-
How do I make a chapter index that is less than
1
(eg the "about this book" section)? -
What does "replaceable" mean?
-
When introducing a new term do I decorate it at all besides the emphasis?
-
Indexing hints, yes or no?
-
Winston:
-
outline
-
promise — what will this talk do?
-
heuristics
-
cycle — say what you’ll say/say it/say it again
-
punctuation — re-situate audience
-
near-miss — "isn’t the concept, but doesn’t miss it by much." (arch vs arch w/o top; arch vs arch where legs are pushed together).
-
ask a qn — rhetorical question. Frequent and answerable - *
-
-
Practice — A real question, on real data, as we’d really do it. I’ll especially try to highlight where you should be disciplined, where you should be clever, and where you should keep it simple
-
Patterns — Reasoning forward from the practical case to show the general patterns that guide its execution
-
Principles — Lastly, the larger philosophy that should guide your thinking