SlideShare a Scribd company logo
Logic Lessons
That Last Generations
      Ian Dees • @undees
    Open Source Bridge 2012
Logic Lessons That Last Generations
Logic Lessons That Last Generations
Logic Lessons That Last Generations
Logic Lessons That Last Generations
Logic Lessons That Last Generations
Logic Lessons That Last Generations
Logic Lessons That Last Generations
The Twinge
The building of things scratches an essential itch for
engineers. It’s why they became engineers in the first place.
                                                —Michael Lopp




                                          flickr.com/photos/ilex/150588521
Logic Lessons That Last Generations
Logic Lessons That Last Generations
Logic Lessons That Last Generations
Logic Lessons That Last Generations
Logic Lessons That Last Generations
Logic Lessons That Last Generations
Logic Lessons That Last Generations
(drink if Markus
mentioned any theorems)
What is this thing?
Logic Lessons That Last Generations
flickr.com/photos/knowprose/5863873076
Logic Lessons That Last Generations
flickr.com/photos/mpieracci/2273915342
1. Tailored to the reader

2. Immediate feedback
Inventing on Principle
           Bret Victor
       vimeo.com/36579366
First things we notice:
Logic Lessons That Last Generations
Logic Lessons That Last Generations
1.Rush to an early victory
1.Rush to an early victory

2.Reward exploration
Dreyfus model
of skill acquisition
     bit.ly/dreyfus-skill
1. Novice

2. Competence

3. Proficiency

4. Expertise

5. Mastery
Logic Lessons That Last Generations
Logic Lessons That Last Generations
Logic Lessons That Last Generations
Logic Lessons That Last Generations
Logic Lessons That Last Generations
Logic Lessons That Last Generations
1.Rush to an early victory

2.Reward exploration

3.Start where your reader is
More puzzles
Logic Lessons That Last Generations
YES  +---------------+        NO
            /--------| Does It Work? |--------
            |         +---------------+             |
            |                                       |
            /                                      /
    +-------------+                            +----------+
    | Don't Mess |                     YES     | Did You | NO
/---| With       It |            /----------|      Mess   |------
|   +-------------+              |             | With It? |       |
|                                |             +----------+       |
|                                /                               |
|                       /------------                            |
|                       | You IDIOT! |                            /
|                       ------------/                   +-------------+
|         +--------+             |                  YES | Will You       |
|      NO | Does |<---------/               /------------| Pay For It? |
|     ----| Anyone |                        |            +-------------+
|   |     | Know ? |--------------         |                     | NO
|   |     +--------+     YES         |      |                     /
|   |                                /  /                 +-----------+
|   |                           /--------------- YES | Will You |
|   |                  /----->| You Poor Fool |<------| Be Fired? |
|   |    /--------- |          ---------------/           +-----------+
|     -->| Hide It | |                  |                         | NO
|        ---------/ |                  /                        |
|              |       | NO +---------------+                     /
|              |       ------| Can You Blame |             /----------
|              |                | Someone Else? |           | Trash It |
|              |                +---------------+           ----------/
|              -------------            | YES                   |
|                             |           |                       |
|                             /         /                       |
|                         +-----------------------+               |
---------------------->| N O P R O B L E M !! |<--------/                   anon.
1.Rush to an early victory

2.Reward exploration

3.Start where your reader is

4.Apply dirty tricks in moderation
Logic Lessons That Last Generations
Logic Lessons That Last Generations
Logic Lessons That Last Generations
1.Rush to an early victory

2.Reward exploration

3.Start where your reader is

4.Apply dirty tricks in moderation

5.Use the head fake
The best way to teach somebody something
is to have them think they’re learning
something else.

              —Randy Pausch, The Last Lecture
0           1




    1   0



0 1     0 0
0           1




    1   0



0 1     0 1
1           0




    0   1



0 0     1 1
Flip-flop
Memory
Comparator
Counter
These are the parts of a computer




                    flickr.com/photos/fimbrethil/137042644
1.Rush to an early victory

2.Reward exploration

3.Start where your reader is

4.Apply dirty tricks in moderation

5.Use the head fake

6.Forge something of value
Logic Lessons That Last Generations
Logic Lessons That Last Generations
Logic Lessons That Last Generations
Logic Lessons That Last Generations
Logic Lessons That Last Generations
1.Rush to an early victory

2.Reward exploration

3.Start where your reader is

4.Apply dirty tricks in moderation

5.Use the head fake

6.Forge something of value

7.Build bridges to other worlds
Final exam
Logic Lessons That Last Generations
Achievement unlocked!




     flickr.com/photos/adafruit/3335282022
Logic Lessons That Last Generations
Tricked into designing a computer
1.Rush to an early victory

2.Reward exploration

3.Start where your reader is

4.Apply dirty tricks in moderation

5.Use the head fake

6.Forge something of value

7.Build bridges to other worlds

8.Support the hero’s quest
A good technical book has a narrative flow. In
many of our books, we try to make it explicit,
starting the books with a story showing the
reader as hero.

    —Dave Thomas, So You Want To Be A Writer
My open questions:
How do we preserve
 Bennett’s legacy?
How do we preserve
   any legacy?
Logic Lessons That Last Generations
>KILL TROLL WITH FLIP-FLOP

YOU CAN'T SEE ANY FLIP-FLOP HERE!
Oral cultures are not just, or even primarily,
about quality assurance in transmission. They
are primarily about quality assurance in
composition, and training in the basic moves
of exposition and condensation.

                              —Venkatesh Rao
How did he do it?
Logic Lessons That Last Generations
1.Rush to an early victory
1.Rush to an early victory

2.Reward exploration
1.Rush to an early victory

2.Reward exploration

3.Start where your reader is
1.Rush to an early victory

2.Reward exploration

3.Start where your reader is

4.Apply dirty tricks in moderation
1.Rush to an early victory

2.Reward exploration

3.Start where your reader is

4.Apply dirty tricks in moderation

5.Use the head fake
1.Rush to an early victory

2.Reward exploration

3.Start where your reader is

4.Apply dirty tricks in moderation

5.Use the head fake

6.Forge something of value
1.Rush to an early victory

2.Reward exploration

3.Start where your reader is

4.Apply dirty tricks in moderation

5.Use the head fake

6.Forge something of value

7.Build bridges to other worlds
1.Rush to an early victory

2.Reward exploration

3.Start where your reader is

4.Apply dirty tricks in moderation

5.Use the head fake

6.Forge something of value

7.Build bridges to other worlds

8.Support the hero’s quest
Logic Lessons That Last Generations
Logic Lessons That Last Generations
Logic Lessons That Last Generations
Logic Lessons That Last Generations

More Related Content

PDF
Security on JIT
PDF
GC in Smalltalk - Now What?
PDF
RBuilder and ByteSurgeon
PDF
Proposals for the Reborn Pharo Developer
PPT
Stoop 390-instruction stream
PPT
Stoop 305-reflective programming5
PPT
Behavioral Reflection
KEY
Your Own Metric System
Security on JIT
GC in Smalltalk - Now What?
RBuilder and ByteSurgeon
Proposals for the Reborn Pharo Developer
Stoop 390-instruction stream
Stoop 305-reflective programming5
Behavioral Reflection
Your Own Metric System

More from Erin Dees (9)

PDF
Thnad's Revenge
PDF
JRuby, Not Just For Hard-Headed Pragmatists Anymore
PDF
Playfulness at Work
PDF
Write Your Own JVM Compiler
PDF
How 5 people with 4 day jobs in 3 time zones enjoyed 2 years writing 1 book
PDF
How 5 people with 4 day jobs in 3 time zones enjoyed 2 years writing 1 book
PDF
A jar-nORM-ous Task
PDF
Cucumber meets iPhone
ZIP
Yes, But
Thnad's Revenge
JRuby, Not Just For Hard-Headed Pragmatists Anymore
Playfulness at Work
Write Your Own JVM Compiler
How 5 people with 4 day jobs in 3 time zones enjoyed 2 years writing 1 book
How 5 people with 4 day jobs in 3 time zones enjoyed 2 years writing 1 book
A jar-nORM-ous Task
Cucumber meets iPhone
Yes, But
Ad

Recently uploaded (20)

PDF
Mobile App Security Testing_ A Comprehensive Guide.pdf
PDF
Build a system with the filesystem maintained by OSTree @ COSCUP 2025
PDF
Diabetes mellitus diagnosis method based random forest with bat algorithm
PDF
Reach Out and Touch Someone: Haptics and Empathic Computing
DOCX
The AUB Centre for AI in Media Proposal.docx
PPT
“AI and Expert System Decision Support & Business Intelligence Systems”
PDF
Profit Center Accounting in SAP S/4HANA, S4F28 Col11
PPTX
Programs and apps: productivity, graphics, security and other tools
PDF
Peak of Data & AI Encore- AI for Metadata and Smarter Workflows
PDF
Spectral efficient network and resource selection model in 5G networks
PDF
Optimiser vos workloads AI/ML sur Amazon EC2 et AWS Graviton
PDF
Agricultural_Statistics_at_a_Glance_2022_0.pdf
PDF
The Rise and Fall of 3GPP – Time for a Sabbatical?
PPTX
sap open course for s4hana steps from ECC to s4
PPTX
Big Data Technologies - Introduction.pptx
PDF
Building Integrated photovoltaic BIPV_UPV.pdf
PPTX
VMware vSphere Foundation How to Sell Presentation-Ver1.4-2-14-2024.pptx
PPTX
Cloud computing and distributed systems.
PPTX
Detection-First SIEM: Rule Types, Dashboards, and Threat-Informed Strategy
PPTX
ACSFv1EN-58255 AWS Academy Cloud Security Foundations.pptx
Mobile App Security Testing_ A Comprehensive Guide.pdf
Build a system with the filesystem maintained by OSTree @ COSCUP 2025
Diabetes mellitus diagnosis method based random forest with bat algorithm
Reach Out and Touch Someone: Haptics and Empathic Computing
The AUB Centre for AI in Media Proposal.docx
“AI and Expert System Decision Support & Business Intelligence Systems”
Profit Center Accounting in SAP S/4HANA, S4F28 Col11
Programs and apps: productivity, graphics, security and other tools
Peak of Data & AI Encore- AI for Metadata and Smarter Workflows
Spectral efficient network and resource selection model in 5G networks
Optimiser vos workloads AI/ML sur Amazon EC2 et AWS Graviton
Agricultural_Statistics_at_a_Glance_2022_0.pdf
The Rise and Fall of 3GPP – Time for a Sabbatical?
sap open course for s4hana steps from ECC to s4
Big Data Technologies - Introduction.pptx
Building Integrated photovoltaic BIPV_UPV.pdf
VMware vSphere Foundation How to Sell Presentation-Ver1.4-2-14-2024.pptx
Cloud computing and distributed systems.
Detection-First SIEM: Rule Types, Dashboards, and Threat-Informed Strategy
ACSFv1EN-58255 AWS Academy Cloud Security Foundations.pptx
Ad

Logic Lessons That Last Generations

  • 1. Logic Lessons That Last Generations Ian Dees • @undees Open Source Bridge 2012
  • 9. The Twinge The building of things scratches an essential itch for engineers. It’s why they became engineers in the first place. —Michael Lopp flickr.com/photos/ilex/150588521
  • 17. (drink if Markus mentioned any theorems)
  • 18. What is this thing?
  • 23. 1. Tailored to the reader 2. Immediate feedback
  • 24. Inventing on Principle Bret Victor vimeo.com/36579366
  • 25. First things we notice:
  • 28. 1.Rush to an early victory
  • 29. 1.Rush to an early victory 2.Reward exploration
  • 30. Dreyfus model of skill acquisition bit.ly/dreyfus-skill
  • 31. 1. Novice 2. Competence 3. Proficiency 4. Expertise 5. Mastery
  • 38. 1.Rush to an early victory 2.Reward exploration 3.Start where your reader is
  • 41. YES +---------------+ NO /--------| Does It Work? |-------- | +---------------+ | | | / / +-------------+ +----------+ | Don't Mess | YES | Did You | NO /---| With It | /----------| Mess |------ | +-------------+ | | With It? | | | | +----------+ | | / | | /------------ | | | You IDIOT! | / | ------------/ +-------------+ | +--------+ | YES | Will You | | NO | Does |<---------/ /------------| Pay For It? | | ----| Anyone | | +-------------+ | | | Know ? |-------------- | | NO | | +--------+ YES | | / | | / / +-----------+ | | /--------------- YES | Will You | | | /----->| You Poor Fool |<------| Be Fired? | | | /--------- | ---------------/ +-----------+ | -->| Hide It | | | | NO | ---------/ | / | | | | NO +---------------+ / | | ------| Can You Blame | /---------- | | | Someone Else? | | Trash It | | | +---------------+ ----------/ | ------------- | YES | | | | | | / / | | +-----------------------+ | ---------------------->| N O P R O B L E M !! |<--------/ anon.
  • 42. 1.Rush to an early victory 2.Reward exploration 3.Start where your reader is 4.Apply dirty tricks in moderation
  • 46. 1.Rush to an early victory 2.Reward exploration 3.Start where your reader is 4.Apply dirty tricks in moderation 5.Use the head fake
  • 47. The best way to teach somebody something is to have them think they’re learning something else. —Randy Pausch, The Last Lecture
  • 48. 0 1 1 0 0 1 0 0
  • 49. 0 1 1 0 0 1 0 1
  • 50. 1 0 0 1 0 0 1 1
  • 55. These are the parts of a computer flickr.com/photos/fimbrethil/137042644
  • 56. 1.Rush to an early victory 2.Reward exploration 3.Start where your reader is 4.Apply dirty tricks in moderation 5.Use the head fake 6.Forge something of value
  • 62. 1.Rush to an early victory 2.Reward exploration 3.Start where your reader is 4.Apply dirty tricks in moderation 5.Use the head fake 6.Forge something of value 7.Build bridges to other worlds
  • 65. Achievement unlocked! flickr.com/photos/adafruit/3335282022
  • 68. 1.Rush to an early victory 2.Reward exploration 3.Start where your reader is 4.Apply dirty tricks in moderation 5.Use the head fake 6.Forge something of value 7.Build bridges to other worlds 8.Support the hero’s quest
  • 69. A good technical book has a narrative flow. In many of our books, we try to make it explicit, starting the books with a story showing the reader as hero. —Dave Thomas, So You Want To Be A Writer
  • 71. How do we preserve Bennett’s legacy?
  • 72. How do we preserve any legacy?
  • 74. >KILL TROLL WITH FLIP-FLOP YOU CAN'T SEE ANY FLIP-FLOP HERE!
  • 75. Oral cultures are not just, or even primarily, about quality assurance in transmission. They are primarily about quality assurance in composition, and training in the basic moves of exposition and condensation. —Venkatesh Rao
  • 76. How did he do it?
  • 78. 1.Rush to an early victory
  • 79. 1.Rush to an early victory 2.Reward exploration
  • 80. 1.Rush to an early victory 2.Reward exploration 3.Start where your reader is
  • 81. 1.Rush to an early victory 2.Reward exploration 3.Start where your reader is 4.Apply dirty tricks in moderation
  • 82. 1.Rush to an early victory 2.Reward exploration 3.Start where your reader is 4.Apply dirty tricks in moderation 5.Use the head fake
  • 83. 1.Rush to an early victory 2.Reward exploration 3.Start where your reader is 4.Apply dirty tricks in moderation 5.Use the head fake 6.Forge something of value
  • 84. 1.Rush to an early victory 2.Reward exploration 3.Start where your reader is 4.Apply dirty tricks in moderation 5.Use the head fake 6.Forge something of value 7.Build bridges to other worlds
  • 85. 1.Rush to an early victory 2.Reward exploration 3.Start where your reader is 4.Apply dirty tricks in moderation 5.Use the head fake 6.Forge something of value 7.Build bridges to other worlds 8.Support the hero’s quest

Editor's Notes

  • #2: This is the story of a book. To paraphrase Douglas Adams, it&amp;#x2019;s the story of &amp;#x201C;a wholly remarkable book.&amp;#x201D; A book that turned a writer from the 1960s into a time traveller, an old engineer into a teacher, and a young boy into an engineer. A book with lessons for all of us, should we choose to listen, about how we explain, how we document, and how we build a legacy, both individually and as a programming community.\n
  • #3: The story of that wonderful, beautiful Thursday, (channeling Adams again) &amp;#x201C;the story of its extraordinary consequences, and the story of how those consequences are inextricably intertwined with this remarkable book begins very simply. It begins with a house.&amp;#x201D;\n
  • #4: Before we get to that, do any of you have an important person in your lives who had a lot to do with your getting into technology? A parent, teacher, or friend? What memories do you have of your path to technology?\n
  • #5: This my grandparents&amp;#x2019; house in East Texas where my family would descend several times a year to ride horses, chase dogs around, and so on.\n
  • #6: That&amp;#x2019;s me among all my cousins. One of my favorite things to do during these visits was watch my grandfather work in his garage laboratory.\n
  • #7: By day, my grandfather was an engineer. By night, he restored and operated radios. To his friends, he was Pete.\n
  • #8: To the FCC, he was W5YNI.\n
  • #9: To me, he was Grampy. I don&amp;#x2019;t know why he put up with my hanging around in his lab. Perhaps he saw my interest in engineering even before I did.\n
  • #10: Rands continues: &amp;#x201C;When they were six, their Dad handed them two boards, a nail, and a hammer and they started whacking. BLAM BLAM BLAM. Even with the nail awkwardly bent in half, the wood was suddenly and magically bound together: a thing was built. At that moment, this junior engineer&amp;#x2019;s brain excreted a chemical that instantly convinced them of the disproportionate value of this construction. This is the best wood thing in the world because I built it. And then they looked up from their creation and pleaded, &amp;#x2018;Dad, I really need more nails.&amp;#x2019;&amp;#x201D;\n
  • #11: One day, Grampy presented me with a plain black three-ring binder. It looked ancient. It had long-abandoned spider nests in the binding. It was dusty and greasy.\n\n
  • #12: When I opened it, I saw yellowed pages bearing the words, &amp;#x201C;Binary Logic,&amp;#x201D; by William S. Bennett.\n
  • #13: The next page confronted me with a simple definition...\n
  • #14: ...followed by a simple puzzle. I&amp;#x2019;m sure you know the answer to this question. But just for fun, let&amp;#x2019;s follow one of the incorrect answers.\n
  • #15: The book sets us gently back on course,....\n
  • #16: ...and we eventually find the correct solution.\n
  • #17: Immediately, we&amp;#x2019;re asked to apply what we&amp;#x2019;ve learned. Which circuit implements the AND gate we&amp;#x2019;ve just read about?\n
  • #18: If Markus Roberts is in the audience, he will cite DeMorgan&amp;#x2019;s Theorem and point out that the answer depends on whether you count a lit light bulb as on or off.\n
  • #19: The book continues in the same style from there. Let&amp;#x2019;s take a step back for a sec. What on earth is this thing?\n
  • #20: The page footer gives us a clue. This was a series of columns that ran in Product Engineering magazine from 1962-3, and again in 1965.\n
  • #21: As near as I can tell, Product Engineering ran from the &amp;#x2018;40s to the &amp;#x2018;60s. It seemed to be kind of like Popular Mechanics for design engineers. Geek-speak meets &amp;#x201C;the flying car of tomorrow.&amp;#x201D;\n
  • #22: This particular column on binary logic was basically a Choose Your Own Adventure book for grown-ups. The editor referred to it as a &amp;#x201C;teaching machine&amp;#x201D; or &amp;#x201C;scrambled book.&amp;#x201D;\n
  • #23: Before we get too excited about the possibilities, observe that the phrase &amp;#x201C;teaching machine&amp;#x201D; reminds us of interfaces that use the customer as a peripheral. As we&amp;#x2019;ll see, this book demands much more active involvement than that.\n
  • #24: Frank Hall, the editor of the magazine, cited research that the &amp;#x201C;scrambled book&amp;#x201D; teaching method lets diverse audiences gain the same skill set at their own pace, and that reinforcement and feedback are crucial parts of the process. \n
  • #25: This emphasis on rapid feedback reminds me of Bret Victor&amp;#x2019;s excellent talk &amp;#x201C;Inventing on Principle,&amp;#x201D; in which he builds extremely interactive user interfaces in the service of a larger point about having a life&apos;s mission.\n
  • #26: Let&amp;#x2019;s go back and look at the puzzle we just solved, and see the way Bennett is already teaching us not just how to understand binary logic, but also how to teach. First, he starts with one easy achievement&amp;#x2014;an early success to hook the reader.\n
  • #27: He leaves easy navigation markers: we always know where we came from and where to go if we get lost.\n
  • #28: So, these are the first two lessons from diving into this work: get your reader to an early success, and don&amp;#x2019;t punish them for veering off the path.\n
  • #29: So, these are the first two lessons from diving into this work: get your reader to an early success, and don&amp;#x2019;t punish them for veering off the path.\n
  • #30: Incidentally, this notion of setting up early obstacles that are just the right difficulty level is related to the Dreyfus model cited by just about everyone these days.\n
  • #31: In this model, you adapt your teaching style to the audience. This implies that the tips we&amp;#x2019;re talking about today are not universal. Bennett&amp;#x2019;s audience was engineers who knew other disciplines, but were novices at binary logic.\n
  • #32: The next thing the book does is present us with an analogy to familiar items.\n
  • #33: Several analogies, in fact, drawing first from simple electrical and mechanical devices.\n
  • #34: In one clever setup, the author even makes his hypothetical mechanical device physically resemble the old schematic symbol for an OR gate.\n
  • #35: The devices get more elaborate; here&amp;#x2019;s another OR gate. Since this device is a series of tubes, it may be a mechanical precursor to the internet. ;-)\n
  • #36: The book branches out into other engineering disciplines, even using optical elements in some examples.\n
  • #37: In other words, Bennett is meeting the reader on their terms.\n
  • #38: Let&amp;#x2019;s look through some more steps in the process.\n
  • #39: After we&amp;#x2019;ve mastered the basics, Bennett introduces some humor. This went over my head at the time; I thought he was saying the measurements were intolerable!\n
  • #40: The schematic resembles that famous Usenet gag about a universal flowchart for diagnosing engineering problems.\n
  • #41: Going for the cheap laugh is of course fine; just do so in moderation.\n
  • #42: Here, Bennett introduces what he says is a labor-saving device: algebraic notation for simplifying logic diagrams.\n
  • #43: But it turns out it was just a backdoor way of preparing us for DeMorgan&amp;#x2019;s theorem...\n
  • #44: ...which basically says you can reverse the meanings of AND, OR, and NOT in a circuit and still get the same result. This is a huge deal in logic design; you can build an entire design out of one kind of component.\n
  • #45: This teaching by misdirection was dubbed a &amp;#x201C;head fake&amp;#x201D; by Randy Pausch,...\n
  • #46: ...in his famous Last Lecture.\n
  • #47: Next, Bennett has us putting building blocks together in bigger combinations. Consider this circuit that folds in on itself.\n
  • #48: As you toggle one of the inputs at the bottom,...\n
  • #49: ...both outputs at the top change state and stay in their new configuration.\n
  • #50: This kind of circuit is known as a flip-flop. It&amp;#x2019;s the foundation of electronic memory.\n
  • #51: If you don&amp;#x2019;t want the inconvenience of two inputs, you can combine them into a single &amp;#x201C;toggle&amp;#x201D; input.\n
  • #52: Once you have one-bit memory cells, you can assemble them into four-bit numbers and compare them.\n
  • #53: You can also chain them one to the next, building a circuit that can count numbers.\n
  • #54: These are the building blocks of a computer! By the end of the course, you&amp;#x2019;ve essentially seen the most important pieces of a CPU.\n
  • #55: Bennett has brought us from &amp;#x201C;this is an AND&amp;#x201D; to &amp;#x201C;go design your own computer.&amp;#x201D; He has given us the power to create value.\n
  • #56: Then, just to drive the point home, he spends another advanced lesson showing us more analogies. Here&amp;#x2019;s a flip-flop made of pulleys.\n
  • #57: Here&amp;#x2019;s another flip-flop; this one&amp;#x2019;s made of moving air! The research to create thin sandwiches of transparent material was new at the time. Bennett was using his column to give us sneak peeks at emerging technologies.\n
  • #58: Here&amp;#x2019;s a NOR gate made of moving fluid...\n
  • #59: ...and an AND gate. He has deliberately chosen these layouts...\n
  • #60: ...to prepare us for the actual implementation of the logic gates in silicon.\n
  • #61: These analogies started out as a warm, fuzzy way to introduce the core teaching concepts, and now they&amp;#x2019;re being used to go the opposite direction: to branch out into new territories.\n
  • #62: The last part of Bennett&amp;#x2019;s course is the final exam.\n
  • #63: If you send in your correct answers and 50 cents handling, you get your very own diploma.\n
  • #64: Remind you of anything?\n
  • #65: We talk a good (ahem) game about gamification these days, but Bennett beat us to the punch by about 40 years.\n
  • #66: By engaging us in this quest, Bennett has basically tricked us into designing a computer. We&amp;#x2019;ve fought our way through obstacle after obstacle, including a final boss.\n
  • #67: This whole journey through the book, culminating in slaying the final dragon and collecting riches, supports the idea of the reader as a hero.\n
  • #68: The Pragmatic Programmers talk about this a lot. In fact, the Author&amp;#x2019;s Guide they distribute to everyone who writes for them contains a whole chapter on the idea.\n
  • #69: And I suppose now&amp;#x2019;s as good a time as any to tell you I&amp;#x2019;m writing another book for them. This one&amp;#x2019;s on Cucumber. I get to sleep at night by telling myself there&amp;#x2019;s a connection to this talk in there somewhere&amp;#x2014;indeed, good tests can tell a story.\n
  • #70: As we move into the final phase of this talk, I&amp;#x2019;d like to talk about a couple of the many questions I&amp;#x2019;ve asked about Bennett&amp;#x2019;s remarkable book.\n
  • #71: First, as delightful as it is that this book is still engaging and relevant, how to we preserve it?\n
  • #72: Indeed, how do we preserve anything?\n
  • #73: One answer is translating into other media. McGraw Hill did republish the work in paperback form in the &amp;#x2018;70s. I&amp;#x2019;ve written them to ask permission to go further, and translate the work into hypertext.\n
  • #74: Perhaps an even better venue would be an interactive story; for more on how to build those, see Bart&amp;#x2019;s talk on Thursday at 10:00.\n
  • #75: The thing about casting things as stories like this is that they have as big of a beneficial impact on the storyteller and the material itself as they do on the listener.\n
  • #76: The other big question is, how did Bennett manage to create this enduring work in the first place? Did he even know how significant his creation would be?\n
  • #77: That brings us back around to the lessons we&amp;#x2019;ve gleaned from looking at this work.\n
  • #78: That brings us back around to the lessons we&amp;#x2019;ve gleaned from looking at this work.\n
  • #79: That brings us back around to the lessons we&amp;#x2019;ve gleaned from looking at this work.\n
  • #80: That brings us back around to the lessons we&amp;#x2019;ve gleaned from looking at this work.\n
  • #81: That brings us back around to the lessons we&amp;#x2019;ve gleaned from looking at this work.\n
  • #82: That brings us back around to the lessons we&amp;#x2019;ve gleaned from looking at this work.\n
  • #83: That brings us back around to the lessons we&amp;#x2019;ve gleaned from looking at this work.\n
  • #84: That brings us back around to the lessons we&amp;#x2019;ve gleaned from looking at this work.\n
  • #85: Speaking of the hero&amp;#x2019;s journey, here&amp;#x2019;s a eulogy written by one of my Grampy&amp;#x2019;s fans. I found it among the family photos I was scouring for material for this talk.\n
  • #86: In particular, see how Grampy taught more people than just me. His passion for engineering is still rippling throughout the universe.\n
  • #87: I don&amp;#x2019;t think Grampy was worried about trying to preserve his legacy. I think he was just doing what he loved, and encouraging others to do the same.\n
  • #88: This means we don&amp;#x2019;t have to sweat this, either. Any one in this room could build something that people are still talking about generations from now. Any one of you could teach one person a skill and see that knowledge spread to thousands. I am standing in a room full of conquerors and heroes, with any luck I&amp;#x2019;ll be around long enough to see the impact of your deeds far and wide. Cheers.\n