What were they thinking? - Speaker Deck

Tweet

Tweet

Slide 1

Slide 1 text

“What were they thinking?” Keith Pitty, RubyConf AU 2019

Slide 2

Slide 2 text

No content

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

⌚

Slide 6

Slide 6 text

❓

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

⏩

Slide 9

Slide 9 text

⏰

Slide 10

Slide 10 text

No content

Slide 11

Slide 11 text

⏰

Slide 12

Slide 12 text

No content

Slide 13

Slide 13 text

No content

Slide 14

Slide 14 text

No content

Slide 15

Slide 15 text

No content

Slide 16

Slide 16 text

How did the code get like that?

Slide 17

Slide 17 text

What was lacking?

Slide 18

Slide 18 text

Design?

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

1. Tests pass 2. Expresses intent 3. No duplication (DRY) 4. Small

Slide 21

Slide 21 text

Refactoring?

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 text

Dependent on automated testing

Slide 24

Slide 24 text

1. Tests pass ✅

Slide 25

Slide 25 text

2. Improve design

Slide 26

Slide 26 text

3. Others will thank us

Slide 27

Slide 27 text

Automated tests?

Slide 28

Slide 28 text

Conﬁdence

Slide 29

Slide 29 text

TDD

Slide 30

Slide 30 text

Continuous Integration

Slide 31

Slide 31 text

Sufﬁcient?

Slide 32

Slide 32 text

What else?

Slide 33

Slide 33 text

Up front design?

Slide 34

Slide 34 text

“Big design up front is dumb. Doing no design up front is even dumber.” — Dave Thomas (YOW! founder)

Slide 35

Slide 35 text

C4 model

Slide 36

Slide 36 text

Improving chances of success

Slide 37

Slide 37 text

Any up front design?

Slide 38

Slide 38 text

Review?

Slide 39

Slide 39 text

e.g. pull requests

Slide 40

Slide 40 text

Early opportunity

Slide 41

Slide 41 text

Temptation

Slide 42

Slide 42 text

Pressure

Slide 43

Slide 43 text

Balance?

Slide 44

Slide 44 text

Documentation?

Slide 45

Slide 45 text

Load testing?

Slide 46

Slide 46 text

Too hard?

Slide 47

Slide 47 text

Cumulative effect

Slide 48

Slide 48 text

No content

Slide 49

Slide 49 text

Planned maintenance?

Slide 50

Slide 50 text

Schedule?

Slide 51

Slide 51 text

Budget?

Slide 52

Slide 52 text

Security patches?

Slide 53

Slide 53 text

Recent Rails release?

Slide 54

Slide 54 text

Reactive?

Slide 55

Slide 55 text

Technical oversight?

Slide 56

Slide 56 text

Sufﬁcient weight?

Slide 57

Slide 57 text

Negotiation with business owner?

Slide 58

Slide 58 text

Sufﬁcient?

Slide 59

Slide 59 text

Alternative?

Slide 60

Slide 60 text

What we neglected!

Slide 61

Slide 61 text

No content

Slide 62

Slide 62 text

What else?

Slide 63

Slide 63 text

Be more disciplined

Slide 64

Slide 64 text

Explain better

Slide 65

Slide 65 text

Negotiating a better outcome

Slide 66

Slide 66 text

Potential pitfalls

Slide 67

Slide 67 text

Alternatives

Slide 68

Slide 68 text

Be positive

Slide 69

Slide 69 text

Goals?

Slide 70

Slide 70 text

Continuous Flow

Slide 71

Slide 71 text

No content

Slide 72

Slide 72 text

No content

Slide 73

Slide 73 text

Continuous “x”

Slide 74

Slide 74 text

Reﬂecting on Agile

Slide 75

Slide 75 text

Explore Agile’s essence

Slide 76

Slide 76 text

Heart of Agile

Slide 77

Slide 77 text

No content

Slide 78

Slide 78 text

Be prepared to explain

Slide 79

Slide 79 text

Don’t try to win arguments!

Slide 80

Slide 80 text

No content

Slide 81

Slide 81 text

No content

Slide 82

Slide 82 text

Shared meaning

Slide 83

Slide 83 text

No content

Slide 84

Slide 84 text

Practice

Slide 85

Slide 85 text

Relative ease

Slide 86

Slide 86 text

Challenge: Persuasion

Slide 87

Slide 87 text

It takes time

Slide 88

Slide 88 text

Patience

Slide 89

Slide 89 text

Persist

Slide 90

Slide 90 text

Consult

Slide 91

Slide 91 text

Keep learning

Slide 92

Slide 92 text

Communication

Slide 93

Slide 93 text

Endurance

Slide 94

Slide 94 text

No content

Slide 95

Slide 95 text

No content

Slide 96

Slide 96 text

No content

Slide 97

Slide 97 text

1. Be more disciplined

Slide 98

Slide 98 text

2. Become more persuasive

Slide 99

Slide 99 text

References • “Understanding the 4 Rules of Simple Design” by Corey Haines • “Refactoring: Improving the Design of Existing Code” by Martin Fowler • Simon Brown’s C4 model: https://c4model.com/ • Simon Brown - “Software Architecture for Developers” at YOW! 2017: https://www.youtube.com/watch?v=z1xLDzx7hgw • “#noprojects - A Culture of Continuous Value” by Evan Leybourn & Shane Hastie • “Continuous Digital - An agile alternative to projects for digital business” by Allan Kelly • Heart of Agile (Alistair Cockburn): https://heartofagile.com/ • Sandi Metz - “You are insufﬁciently persuasive” at RubyConf AU 2018: https://www.youtube.com/watch?v=Y3k7tHll3RY • “Crucial Conversations - Tools for Talking When Stakes Are High” by Kerry Patterson, Joseph Grenny, Ron McMillan, Al Switzler

Slide 100

Slide 100 text

Image credits • https://unsplash.com/photos/1K9T5YiZ2WU - Photo by Tim Gouw on Unsplash • https://unsplash.com/photos/-IMlv9Jlb24 - Photo by Sebastien Gabriel on Unsplash • https://unsplash.com/photos/aWJ-QqrSU_E - Photo by Harrison Broadbent on Unsplash • https://unsplash.com/photos/lu15z1m_KfM - Photo by Lili Popper on Unsplash • https://heartofagile.com/wp-content/uploads/2018/09/hero_graphic2.png - Image courtesy of Alistair Cockburn

Slide 101

Slide 101 text

Thanks for listening!