by Andy Hunt
I, Michael Parker, own this book and took these notes to further my own learning. If you enjoy these notes, please purchase the book!
- pg 13: Programming is all about problem solving. It requires creativity, ingenuity, and invention.
- pg 14: Software isn't designed in an IDE or other tool. It’s imagined and created in our heads.
- pg 15: Two of the most important modern skills are communication, and learning and thinking.
- pg 26: Event theories can be measured, verified, and proven. Construct theories are intangible abstractions, cannot be proven, and are evaluated by usefulness.
- pg 28: It's often difficult for experts to explain their actions to a fine level of detail; many of their responses are so well practiced that they become preconscious actions.
- pg 29: Novices need clear, context-free rules by which they can operate, just as the expert would be rendered ineffective if he were constrained to operate under those same rules.
- pg 29: When becoming an expert, you don't just know more, but you experience fundamental differences in how you perceive the world, how you approach problem solving, and the mental models you form and use.
- pg 30: At stage 1 of the Dreyfus model, novices can be somewhat effective by following context-free rules, but are vulnerable to confusion when mistakes happen or things go awry.
- pg 32: At stage 2, advanced beginners try things on their own, take advice, and want information fast, but still have problems troubleshooting and don't see a big picture.
- pg 33: At stage 3, competent practitioners can develop and use mental models, troubleshoot problems on their own, and find and apply advice from experts.
- pg 34: At stage 4, proficient practitioners can correct previous poor task performance, learn from the experience of others, and know what likely happens next or what can break.
- pg 36: At stage 5, experts are primary sources of knowledge, continually look for better methods, and work from intuition instead of reason.
- pg 39: Novices following rules by experts thrive, while experts following rules by other experts suffer. Their tool is intuition.
- pg 40: Three most important changes are moving from rules to intuition, equal weighting of parts to distinguishing important and unimportant ones, and detached observer to involved influencer.
- pg 42: Most people are advanced beginners who overstate their abilities (the Dunning-Kruger effect) because metacognitive abilities tend to only appear at higher skill levels.
- pg 43: A competent practitioner might be better suited to teach a novice than an expert, who are often unable to articulate why they reached a particular decision.
- pg 44: Deliberate practice requires tackling a well-defined and appropriately difficult task, in an environment that provides feedback and provides opportunities for repetition and correction of errors.
- pg 47: To help promote the skills of advanced beginners to competent practitioners, have good exemplars in the environment; they will be watched and imitated.
- pg 48: Trumpeter Clark Terry told students the secret to learning music was to imitate, assimilate, and then innovate.
- pg 51: Tools and models are useful in the right environments, but none are a panacea, and their misapplication has probably done more damage than good.
- pg 53: Avoid formal rules if you need creativity, intuition, or inventiveness.
- pg 55: Context matters, as the expert uses context-dependent intuition, but the lower stages of the Dreyfus model aren't skilled enough to use it.
- pg 59: The R-mode of your brain is critical for intuition, problem solving, and creativity. The L-mode gives you the power to work through the details and make it happen.
- pg 61: Memory is actively maintained by an executing loop. Like dynamic RAM, your brain needs constant refreshing, or its memories fade.
- pg 62: Like describing a dream, R-mode yields many results that can't be verbalized. Additionally, it's like peripheral vision, outside your direct control.
- pg 63: R-mode is unpredictable, so you need to be ready to capture any insight or idea at any time.
- pg 66: Once you start keeping track of ideas, you'll get more of them. Everyone has good ideas to capture.
- pg 71: L-mode gives you verbal, analytic, symbolic, abstract, temporal, rational, digital, logical, and linear thinking abilities.
- pg 72: R-mode is non-verbal, non-rational, synthetic to compose and form wholes, spatial, concrete, intuitive, analogic, and holistic to recognize patterns and structures. This is where intuition lies.
- pg 74: Building things you can learn from, like prototypes and unit tests, is R-mode synthesis; inspecting and dissecting is L-mode analysis.
- pg 78: When you are fearful or angry, filled with negative emotions, your body shuts down extra resources in preparation for for fight or flight.
- pg 80: Creativity comes from the selection of the right components in the right presentation to create the work. And selection comes from pattern matching.
- pg 81: R-mode helps you find global, holistic patterns. L-mode lets you analyze parts and look into the detail.
- pg 83: Believing in the plasticity of your brain, or the amount you can learn and number of skills you can attain, increases those abilities.
- pg 85: Activate more neural pathways than usual to involve more of your brain. For example, fiddle with a tactile puzzle while pondering a tricky problem.
- pg 86: Allow several senses to interact, like writing a problem down, drawing it, describing it verbally, engaging in open discussion, and act out roles.
- pg 88: Listening to music, drawing, meditation, jogging, needlework, rock climbing, and so on can engage the R-mode that shuts off the L-mode.
- pg 92: Once you experience the shift to R-mode, you'll better know what R-mode processing feels like, and it will become easier over time.
- pg 94: You want to let the R-mode lead and then switch to the L-mode to "productize" it.
- pg 98: Working together is an effective way to discover helpful and interesting abstractions. In pair programming, the driver is in L-mode, while the navigator is in R-mode.
- pg 99: A strong metaphor comes from suddenly switching from one frame of reference to a different, unexpected one. That junction between the two frames is the bisociation.
- pg 100: The farther away the ideas are, the harder it is to join them in a metaphor that works. But such imprinting from one frame to another is very powerful.
- pg 101: Programmers are sloppy in their use of metaphors. For example, using
insert()
instead ofadd()
on a container, tables that aren't like tables, threads that aren't like threads. - pg 103: Humor comes from drawing or extending relationships beyond the norm, which also helps build stronger metaphors.
- pg 104: Your brain stores every input it receives, although does not necessarily index them. Your R-mode asynchronously scans these memories, albeit inefficiently.
- pg 107: Image streaming harvests R-mode imagery: Pose a question, then close your eyes, and describe out loud every image that crosses your mind. Imagine it using all five senses.
- pg 110: With the morning pages technique, write three uncensored pages long hand before you "wake up." This gives you an unguarded, unconscious R-mode brain dump.
- pg 112: Insight can come at odd times like taking a shower or mowing the lawn because the L-mode gets bored and tunes out, leaving the R-mode to present its findings.
- pg 114: As Poincaré did, write down everything you know about a problem, and then go on a walk without focusing on it, allowing the R-mode to dominate.
- pg 115: Making source code human-readable means making the larger patterns in the code easier to see.
- pg 117: Use consistent typographic cues to aid visual perception. Conflicting styles are contentious because they represent conflicting patterns.
- pg 118: Change your viewpoint on a problem by viewing it in reverse, exaggerating an idea, combining disparate ideas, and non-goal-directed playing with ideas.
- pg 121: Even small changes in your routine, like where you park, where you part your hair, when you eat, and what days you shave help prevent neural ruts.
- pg 126: Cognitive biases are mental "bugs" that affect your decision making, memory, perception, rationality, and so on. There are a lot of them.
- pg 128: Symbolic reduction, or reducing large, complex systems to simple, easily manipulated symbols, is essential to computer programming and knowledge-based work.
- pg 129: Humans are bad at trying to extrapolate future events from previous ones. We assume a stable, linear progression, with easily defined cause and effect.
- pg 131: Don't discount unobserved or rare phenomena as impossible. And homogeneity and randomness are different things.
- pg 132: On an exploratory or inventive project, you learn as you go, and so you know most at the end. So defer closure in order to make better decisions later.
- pg 133: Agile development embraces uncertainty; it is not a bad thing. Chip away at the details, and don't nail them down until ready.
- pg 134: Write things down. As a Chinese proverb says, the palest ink is better than the best memory.
- pg 136: Attitudes on risk, individualism vs teamwork, stability vs freedom, and family vs work are affected by your cohort and your parents.
- pg 139: Generation X form the greatest entrepreneurial generation in U.S. history. They're fiercely individualistic, and resist being labeled at all costs.
- pg 141: The four generational archetypes are the prophet, with vision, values; the nomad, with liberty, survival, honor; the hero, with community, affluence; and the artist, with pluralism, expertise, due process.
- pg 142: With Howe/Strauss generational archetypes, the hero begets the artist, who begets the prophet, who begets nomad, who begets the hero.
- pg 143: The best way to keep from falling victim to your generation’s particular set of biases is to embrace diversity.
- pg 144: Within the MBTI framework, sensing (S) vs intuition (N) is probably the largest source of miscommunication and misunderstanding. 75 percent of folks are sening.
- pg 146: Work out a compromise. Do not try to change the other person’s temperament to match your own.
- pg 148: Our primeval characteristics include immediate fight or flight, wanting everything now, being dominant, defending territory, crying foul, and considering anyone different evil.
- pg 149: Attitudes, beliefs, behaviors, and emotions are all contagious.
- pg 150: It's easy to write a short and snippy e-mail because it doesn't give the neocortex time to intervene, unlike writing a longhand letter.
- pg 152: Lead with intuition, but follow up with provable, linear feedback. Your intuition may be wrong.
- pg 153: Expectations color reality. So ask hard questions about a problem, measure all you can, get the opinion of others, and define its opposite to draw a more critical eye.
- pg 157: Learning isn't done to you, it's something you do. "Education" comes from "educare," which literally means "led out." And knowledge alone, without experience, isn't effective.
- pg 159: To develop competence and expertise, you need continuing goals, feedback to understand your progress, and a deliberate approach to the whole thing.
- pg 160: An objective is something you do to get you closer to a goal. It should be specific, measurable, achievable, relevant, and time-boxed. Together, SMART objectives.
- pg 165: By being deliberate about your learning, by allocating appropriate time, and by using that time wisely, you can be much more efficient in your learning.
- pg 166: All knowledge investments have some value. Even if you never use a particular technology vocationally, it will impact the way you think and solve problems.
- pg 167: Not all learning sessions will be equally productive, but by scheduling them regularly, you will win out in the long run.
- pg 169: Visual learners need to see the material, auditory learners need to hear the material, and kinesthetic learners need to physically experience the material.
- pg 171: Howard Gardner defined seven facets of intelligence: kinesthetic, linguistic, logical/mathematical, visual/spatial, musical, interpersonal, and intrapersonal.
- pg 176: The team that studies together learns together, teaches each other, and learns more effectively.
- pg 177: Written instructions are considered the least efficient because many parts of the brain and body you want to train or educate aren't the parts that process language.
- pg 178: After surveying the work, forming questions, and then reading, recite the information by playing with it, exercising your R-mode. Finally, review it.
- pg 180: Reading the same material over and over doesn't help you remember it. Instead, test yourself by trying to recall the material over and over.
- pg 183: Redrawing a mind map from memory helps strengthen the connections and may expose additional insights in the process.
- pg 186: For exploratory mind maps, use words as titles, draw icons to represent key ideas, and make important lines thick. Do it quickly, giving the R-mode unfettered access.
- pg 188: For a collaborative mind map, write ideas on stick notes, cluster related notes together, and draw circles around each group and connect them with lines.
- pg 190: Documenting makes you turn your attention inward, as you would when working with a mind map, promoting insight later in the project.
- pg 191: Teaching others clarifies your own understanding of something and reveals many of your underlying assumptions.
- pg 195: Non-goal-directed exploring, or playing with a problem, doesn't make it any easier, but it gets us closer to how we're wired to learn.
- pg 196: Working with new material or solving a problem in a playful manner makes it more enjoyable and also easier to learn.
- pg 199: When learning from similarities, clinging to them thinking may prevent us from fully embracing a new skill. And our notion of "similar" may be completely wrong.
- pg 200: "I don't know" is a fine answer, but don't let it end there. And it's not important to get something right the first time; it's important to get it right the last time.
- pg 202: Version control allows backtracking; unit testing measures progress; automation ensures repetition. Together, they give you the ability to experiment with little risk.
- pg 204: Inner game stresses learning from your own experience. It's difficult to learn something by words; we learn something better by discovery, not instruction.
- pg 206: When playing the inner game, just be aware. Don't try to get it right, but notice when it's wrong, and act to correct it.
- pg 207: When debugging, be fully aware of how the system is behaving, and then decide what part is wrong before moving on to devise a solution.
- pg 209: Not only does your creativity suffer with a deadline looming, but it suffers for two days after the deadline. So end a project iteration on a Friday.
- pg 211: Once you create an environment where it's acceptable to fail, the pressure is off, and you can be attentive, comfortable, and observant. See unit testing and prototyping.
- pg 214: Much of perception is based on prediction, which is based on context and past experience, so much that current, real-time input takes a backseat.
- pg 216: You can imagine experiences and learn from as effectively as if you had lived them for real, because your brain has difficulty telling the difference.
- pg 217: Intuition grows by having more patterns to draw on and apply, and a growing body of tacit knowledge of what to look for and when.
- pg 219: Information is raw data in a given context, while knowledge imparts meaning to that information, from the application of time, attention, or skill.
- pg 221: Much of meditation, yoga, and similar practices offer some relief from the idle chatter of your L-mode, to live in the moment, and to not divide your mental energy unnecessarily.
- pg 223: With Vipassana meditation, explicitly focus on your breathing. Words can come, but just let them go, and return attention to your breath.
- pg 224: With the segmented breath controlled breathing approach, on the inhale, fill the lower belly first, then the chest, and then finally up to the collar bones.
- pg 226: Handing over work to the unconscious only works if you have some data to fill up on.
- pg 229: Tools you use for mental support outside your brain become part of your operating mind. They help form your exocortex.
- pg 233: Whether a wiki or a shoebox, once you have a place or page to put some type of thought, you'll get more thoughts of that type.
- pg 235: Transcribing notes to the wiki or cleaning them up on the wiki helps get your head around the material.
- pg 236: Multitasking can cost you 20 to 50 percent of your productivity, while after an interruption it make 20 minutes to pick up where you left off.
- pg 241: GTD suggests scanning the input queue only once, processing each pile of work in order, and not keeping lists in your head.
- pg 243: Set up times of the day when you aren't to be interrupted, and other times for collaboration, daily stand-up meetings, and other assorted contingencies.
- pg 245: To control the flood of email, remember that you'll receive less email if you send less email, and that your reply speed sets the tempo for a conversation.
- pg 246: To try and keep context, raise the physical cost of entry and exit to remind you of the mental cost.
- pg 247: In the few seconds before an interruption takes hold, leave some breadcrumbs or cues that you can pick up on when you get back to resuming the task.
- pg 248: You can instantly recognize productivity gains of 20 to 30 percent with a second monitor. Get one of the same size and brand to minimize distractions.
- pg 250: Organize virtual desktops by task, such as communications, writing, coding, surfing, and music.
- pg 254: To manage effective change, remember: Start with a plan, fear inaction and not error, give it a fair chance, believe that change is possible, and take small and achievable steps.
- pg 256: The professional kiss of death for the expert is to act like one. Your own judgment and views, instead of supporting you, can imprison you.
- pg 257: Leonardo Da Vinci said: "People look without seeing, hear without listening, eat without awareness of taste, touch without feeling, and talk without thinking."