Climbing Rocks & Coding Blocks
•
1 like•225 views
This document discusses various topics related to software development such as problem solving, dealing with failure, continuous improvement, and diversity in teams. It emphasizes practicing and learning from failures, adopting a growth mindset, finding passion in problems, and improving skills through measurement, mentorship, and focusing efforts. Diversity is highlighted as an important factor in team performance, and creating an inclusive environment where all voices are heard is encouraged.
Recommended
Recommended
More Related Content
Similar to Climbing Rocks & Coding Blocks
Similar to Climbing Rocks & Coding Blocks (20)
Recently uploaded
Recently uploaded (20)
Climbing Rocks & Coding Blocks
- 1. Climbing Rocks & Coding Blocks
- 4. Tabs over Spaces * {border: 1px solid red;} Sandi Metz is my dev hero
- 5. I like animated gifs This might be a self portrait
- 7. ?
- 8. Let’s thank our conference organizers!
- 11. (C) 2010 Walt Disney Pictures.
- 14. (C) 2010 Walt Disney Pictures.
- 16. &
- 17. 1.BREAKING DOWN THE PROBLEM 2.KEEP CALM & CODE ON 3.GEMBA 4.CONTINUOUS IMPROVEMENT - KAIZEN 5.WHAT DOES STAR WARS HAVE TO DO WITH THIS? 6.STUCK BETWEEN A ROCK AND A CODE PLACE 7.WHO IS MATZ?
- 19. Scary place to be
- 20. Scary place to be
- 26. Jumping In The Confident generally have experience and skills Hypothesize and experiment effectively Used to failure Used to meaningful failure Understand feedback Know when to stop Understand succeeding by accident ...quickly. Failure seems safe and practical.
- 27. Jumping In
- 28. Ethan Pringle goes for a huuuuge ride on La Reina Mora (8c+/5.14d) at Siurana, Spain.
- 38. Planning
- 39. Planning Think through the Problem
- 40. Planning
- 41. Planning
- 42. Thinking and analyzing while doing is hard. gravity
- 43. Thinking and analyzing before doing CONSERVES ENERGY. gravity
- 47. 2. KEEP CALM & CODE ON
- 50. FAILURE IS REAL.
- 51. FAILURE IS REAL. O...or is it?
- 52. What we believe about failure
- 54. Failure is bad
- 55. Failure means you’re dumb
- 57. We also believe being smart means winning
- 58. The New York Times: The Competing View on Competition JUST before bedtime on a recent night, two toddlers marched reluctantly to the bathroom to brush their teeth. And on the way, my four-year-old son told his little sister: “I’m going to win. I’m going to win!” At toothbrushing.
- 59. We believe others define smart
- 61. 110% 4.5GPA “Above and Beyond” “Try hard” “Shows initiative” “Clever”
- 63. 05.18.17 The Five Types Of Impostor Syndrome And How To Beat Them 1. The Perfectionist 2. The Superwoman/man 3. The Natural Genius 4. The Rugged Individualist 5. The Expert 3. THE NATURAL GENIUS People who struggle with this...judge success based on their abilities as opposed to their efforts. In other words, if they have to work hard at something, they assume they must be bad at it. These types of impostors set their internal bar impossibly high, just like perfectionists. But natural genius types...judge themselves based on getting things right on the first try. When they’re not able to do something quickly or fluently, their alarm sounds. 5. THE EXPERT People who fall into this competence type may feel like they somehow tricked their employer into hiring them. They deeply fear being exposed as inexperienced or unknowledgeable.
- 66. the good news
- 69. Arianna Huffington dropped out of governor's race from lack of support 10 Highly Successful People on the Times They Got Rejected Jul 30, 2017 Jay-Z couldn't get anyone to put out his record Jeff Bezos's prime flop Stephen King's first book was rejected by 30 publishers
- 70. Reframe the “Failure” mindset. Failure is Feedback. Failure is a Change Agent.
- 71. 3. GEMBA
- 73. PRACTICE
- 74. PRACTICE failing
- 75. PRACTICE failing
- 78. ● git revert ● git reset ● git commit --amend -m ● git diff ● git blame → git praise Priming for failure Practice reversing expected failures
- 79. 1. Set yourself up for failure 2. Reverse the failure “I failed but I was right.”
- 80. “I failed but I was right.”
- 81. Practicing with Expected Failure Prepares You for Unexpected Failure
- 82. SCIENTIFIC RESEARCH MASS CONSTRUCTION Knowable with certainty upfront Responses to unknowns certain SoftwareProduct Development PhysicalProduct Development EnterpriseERP Implementation ComplexManufacturing RoutineManufacturing SPECTRUM OF DOMAIN (UN)CERTAINTY
- 83. PRACTICE
- 86. Practice on Production Code
- 88. PRACTICE
- 89. PRACTICE
- 92. Mastery ● ● ●
- 93. Mastery ●
- 94. Measurement
- 97. Kanban To Do Doing Done
- 98. Retrospective
- 100. Mentorship
- 101. …
- 102. GAPS IN EXPERIENCE
- 103. BRIDGING GAPS
- 104. BRIDGING GAPS git config user.name "Chris Wilson and John Smith"
- 105. Effective Mentorship can mean different things to different people
- 106. WHAT DOES STAR WARS HAVE TO DO WITH THIS?
- 107. 5. FOLLOW YOUR BLISS
- 111. My favorite problem
- 112. Passion Projects
- 115. How long should I hangout between a rock and a code place?
- 117. Don’t let this happen to you.
- 118. Yerkes–Dodson law Find your sweet spot
- 119. FOCUS
- 120. OTHER TECHNIQUES
- 124. 7. MINASWAN
- 125. WHO IS THIS GUY?
- 127. Community matters Brooklyn Boulders Flatiron School Class 03
- 128. DIVERSITY
- 129. PROJECT ARISTOTLE
- 131. ‘‘As long as everyone got a chance to talk, the team did well. But if only one person or a small group spoke all the time, the collective intelligence declined.’’
- 132. Feb. 26, 2016
- 133. Be Nice
- 134. 1.BREAKING DOWN THE PROBLEM 2.KEEP CALM & CODE ON 3.WALK THE GEMBA 4.CONTINUOUS IMPROVEMENT - KAIZEN 5.FOLLOW YOUR BLISS 6.DEALING WITH DIFFICULTY 7.MINASWAN
- 135. Climbing Rocks Coding Blocks
- 136. Climbing Rocks & Coding Blocks Ilikehighfives!