Slide 1

Slide 1 text

https://codon.com/get-off-the-tightrope GET OFF THE TIGHTROPE

Slide 2

Slide 2 text

A very common problem.

Slide 3

Slide 3 text

CTO, FutureLearn

Slide 4

Slide 4 text

It affects everyone.

Slide 5

Slide 5 text

BAD NEWS: it’s serious. GOOD NEWS: it’s fixable.

Slide 6

Slide 6 text

THE PROBLEM THE SYMPTOMS THE CAUSES SOME REMEDIES WHY IS THIS IMPORTANT?

Slide 7

Slide 7 text

THE PROBLEM

Slide 8

Slide 8 text

Trying to do a big thing all at once.

Slide 9

Slide 9 text

A large task, all in your head.

Slide 10

Slide 10 text

One long, precarious, all-or-nothing tightrope walk.

Slide 11

Slide 11 text

THE SYMPTOMS

Slide 12

Slide 12 text

It’s stressful and hard to get right.

Slide 13

Slide 13 text

You disappear down rabbit holes.

Slide 14

Slide 14 text

You get too invested in your early mistakes.

Slide 15

Slide 15 text

You learn to hate interruptions & distractions.

Slide 16

Slide 16 text

(Tech culture reinforces this view.)

Slide 17

Slide 17 text

http://heeris.id.au/2013/this-is-why-you-shouldnt-interrupt-a-programmer/

Slide 18

Slide 18 text

https://twitter.com/phil_wade/status/896010517617180672

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

It takes a long time to pick up your thread again.

Slide 21

Slide 21 text

irritability about questions and meetings worrying you’ll forget what to do next typing “git status” and seeing twenty files modified a big long branch with lots of commits saying “WIP”, “fix stuff”, “changed my mind”, “redo this later”

Slide 22

Slide 22 text

THE CAUSES

Slide 23

Slide 23 text

Eager to make progress.

Slide 24

Slide 24 text

Unsure how big it’s going to be.

Slide 25

Slide 25 text

Unsure how far you have to go.

Slide 26

Slide 26 text

Belief that programmers are special.

Slide 27

Slide 27 text

This is flattering, but misguided.

Slide 28

Slide 28 text

Opportunities for empathy & collaboration.

Slide 29

Slide 29 text

SOME REMEDIES

Slide 30

Slide 30 text

Planning ahead.

Slide 31

Slide 31 text

Story mapping

Slide 32

Slide 32 text

CUSTOMER BUYS PRODUCT View product page Add product to basket Enter payment details View basket page Confirm order Ship product Enter shipping details Cancel order

Slide 33

Slide 33 text

CUSTOMER BUYS PRODUCT Remove product from basket Update old payment details Save product for later Request refund Browse related products Search all products Update product quantity in basket Add product to wishlist

Slide 34

Slide 34 text

CUSTOMER BUYS PRODUCT time

Slide 35

Slide 35 text

CUSTOMER BUYS PRODUCT time ? ?? ?

Slide 36

Slide 36 text

CUSTOMER BUYS PRODUCT Charge credit card Refund credit card Send refund confirmation email Send order confirmation email Filter search results Enter voucher code Sort search results Apply 3-for-2 offer

Slide 37

Slide 37 text

CUSTOMER BUYS PRODUCT

Slide 38

Slide 38 text

CUSTOMER BUYS PRODUCT

Slide 39

Slide 39 text

CUSTOMER BUYS PRODUCT

Slide 40

Slide 40 text

Story mapping breaks down your big problem into small, achievable subproblems.

Slide 41

Slide 41 text

History hygiene.

Slide 42

Slide 42 text

Make small, focused commits.

Slide 43

Slide 43 text

Write commit messages that explain your thinking.

Slide 44

Slide 44 text

Keep your branch in good shape.

Slide 45

Slide 45 text

Don’t diverge too far from master.

Slide 46

Slide 46 text

origin/master my-branch

Slide 47

Slide 47 text

origin/master my-branch

Slide 48

Slide 48 text

my-branch origin/master

Slide 49

Slide 49 text

Cherry-pick preparatory work onto master.

Slide 50

Slide 50 text

origin/master my-branch

Slide 51

Slide 51 text

origin/master my-branch

Slide 52

Slide 52 text

my-branch origin/master

Slide 53

Slide 53 text

Use interactive rebase, early and often.

Slide 54

Slide 54 text

Introduce Foo Clarify text in UI Rename Foo to Bar Improve performance

Slide 55

Slide 55 text

Introduce Foo Clarify text in UI Rename Foo to Bar Improve performance

Slide 56

Slide 56 text

Introduce Foo Clarify text in UI Rename Foo to Bar Improve performance

Slide 57

Slide 57 text

Introduce Foo Clarify text in UI Improve performance Rename Foo to Bar Introduce Bar

Slide 58

Slide 58 text

Practice switching away.

Slide 59

Slide 59 text

Test- driven development.

Slide 60

Slide 60 text

Learn to switch between the mental modes of red-green-refactor.

Slide 61

Slide 61 text

Remember that red-green-refactor is a powerful mind hack.

Slide 62

Slide 62 text

Work outside-in with acceptance tests.

Slide 63

Slide 63 text

Write tests that really do check what you care about.

Slide 64

Slide 64 text

Notes and conversations.

Slide 65

Slide 65 text

Take notes and write down questions as you find them.

Slide 66

Slide 66 text

Practice explaining your train of thought.

Slide 67

Slide 67 text

Talk to other people about what you’re doing and why.

Slide 68

Slide 68 text

Planning ahead. History hygiene. Test-driven development. Notes & conversations.

Slide 69

Slide 69 text

Make your own solutions.

Slide 70

Slide 70 text

Notice the risk, then break it down.

Slide 71

Slide 71 text

Some resources. http://jpattonassociates.com/user-story-mapping/ User Story Mapping https://about.futurelearn.com/blog/telling-stories-with-your-git-history Telling stories with your Git history http://www.growing-object-oriented-software.com/ Growing Object-Oriented Software Guided by Tests https://pragprog.com/book/rspec3/effective-testing-with-rspec-3 Effective Testing with RSpec 3

Slide 72

Slide 72 text

Ashley Ellis Pierce, Git Driven Refactoring

Slide 73

Slide 73 text

Valerie Woolard Srinivasan, How I Learned to Stop Worrying and Love Unit Testing Noel Rappin, High Cost Tests and High Value Tests

Slide 74

Slide 74 text

WHY IS THIS IMPORTANT?

Slide 75

Slide 75 text

Great developers are great at this.

Slide 76

Slide 76 text

Great developers are persistent, have strategies, and apply them methodically.

Slide 77

Slide 77 text

This gets easier with practice.

Slide 78

Slide 78 text

https://codon.com/get-off-the-tightrope THANKS. @tomstuart