Sometimes a Controller is Just a Controller

Slide 1

Slide 1 text

No content

Slide 2

Slide 2 text

Fancy Code

Slide 3

Slide 3 text

vs Fancy Code

Slide 4

Slide 4 text

boring code vs Fancy Code

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

Boring code is so much easier to read!

Slide 9

Slide 9 text

Turns out, that'd be a boring talk

Slide 10

Slide 10 text

Slides

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

I am not an artiste

Slide 13

Slide 13 text

I am not an artiste

Slide 14

Slide 14 text

I am not an artíste

Slide 15

Slide 15 text

I am not an artìste

Slide 16

Slide 16 text

Artists say "I love your slides"

Slide 17

Slide 17 text

Artists say "I love your slides" ! :crying with tears of joy:

Slide 18

Slide 18 text

"Really, I love that you put so much time into your slides"

Slide 19

Slide 19 text

"Really, I love that you put so much time into your slides" " :loudly crying face:

Slide 20

Slide 20 text

Time

Slide 21

Slide 21 text

Time ⏰

Slide 22

Slide 22 text

Time

Slide 23

Slide 23 text

No content

Slide 24

Slide 24 text

Horological Study:

Slide 25

Slide 25 text

Horological Study: time -slides= 0

Slide 26

Slide 26 text

People Won Over

Slide 27

Slide 27 text

0% 20% 40% 60% 80% 100% 1 hour 10 hours 20 hours 40 hours 60 hours People Won Over

Slide 28

Slide 28 text

0% 20% 40% 60% 80% 100% 1 hour 10 hours 20 hours 40 hours 60 hours People Won Over

Slide 29

Slide 29 text

0% 20% 40% 60% 80% 100% 1 hour 10 hours 20 hours 40 hours 60 hours People Won Over

Slide 30

Slide 30 text

0% 20% 40% 60% 80% 100% 1 hour 10 hours 20 hours 40 hours 60 hours People Won Over

Slide 31

Slide 31 text

0% 20% 40% 60% 80% 100% 1 hour 10 hours 20 hours 40 hours 60 hours People Won Over

Slide 32

Slide 32 text

0% 20% 40% 60% 80% 100% 1 hour 10 hours 20 hours 40 hours 60 hours People Won Over

Slide 33

Slide 33 text

0% 20% 40% 60% 80% 100% 1 hour 10 hours 20 hours 40 hours 60 hours People Won Over X

Slide 34

Slide 34 text

0% 20% 40% 60% 80% 100% 1 hour 10 hours 20 hours 40 hours 60 hours People Won Over X

Slide 35

Slide 35 text

80 / 20 Rule

Slide 36

Slide 36 text

0% 20% 40% 60% 80% 100% 1 hour 10 hours 20 hours 40 hours 60 hours People Won Over X

Slide 37

Slide 37 text

0% 20% 40% 60% 80% 100% 1 hour 10 hours 20 hours 40 hours 60 hours People Won Over X

Slide 38

Slide 38 text

Time ⏰

Slide 39

Slide 39 text

No content

Slide 40

Slide 40 text

Sometimes a slide is just a slide

Slide 41

Slide 41 text

"Good" Talk

Slide 42

Slide 42 text

But anyway

Slide 43

Slide 43 text

Good Code

Slide 44

Slide 44 text

1. tiny units

Slide 45

Slide 45 text

1. tiny units 1a. no, like hilariously tiny

Slide 46

Slide 46 text

1. tiny units 1a. no, like hilariously tiny 1b. as in, units with one public method

Slide 47

Slide 47 text

1. tiny units 1a. no, like hilariously tiny 1b. as in, units with one public method 1c. extract privates from complex code for the name, not the abstraction

Slide 48

Slide 48 text

Slide 49

Slide 49 text

Slide 50

Slide 50 text

Slide 51

Slide 51 text

Slide 52

Slide 52 text

Slide 53

Slide 53 text

Slide 54

Slide 54 text

1. tiny units 1a. no, like hilariously tiny 1b. as in, units with one public method 1c. extract privates from complex code for the name, not the abstraction 2. units can hold & describe a value or perform useful behavior, never both 3. behavior-ey units can contain logic or depend on other units, not both 4. eliminate local variables to an absurd degree 4a. start with functional chains 4b. refactor via functional composition 4c. use tap/each as if to scream "Side Effect!" 5. minimize third-party dependencies and write wrappers around them

Slide 55

Slide 55 text

Slide 56

Slide 56 text

Slide 57

Slide 57 text

Slide 58

Slide 58 text

The end.

Slide 59

Slide 59 text

My name is Justin Searls Please tweet me @searls & Say [email protected]

Slide 60

Slide 60 text

( ͠° ͟ʖ ͡°)

Slide 61

Slide 61 text

( ͡~ ͜ ʖ ͡°)

Slide 62

Slide 62 text

My Favorite Way

Slide 63

Slide 63 text

Your Favorite Way

Slide 64

Slide 64 text

Your Team's Favorite Way

Slide 65

Slide 65 text

Your Framework's Favorite Way

Slide 66

Slide 66 text

Your Boss's Favorite Way

Slide 67

Slide 67 text

Your Boss's Favorite Way $

Slide 68

Slide 68 text

Your Boss's Favorite Way ⏰ $

Slide 69

Slide 69 text

Your Boss's Favorite Way % ⏰ $

Slide 70

Slide 70 text

Text (video)

Slide 71

Slide 71 text

If you combine everybody's favorite way then maybe…

Slide 72

Slide 72 text

Good Code

Slide 73

Slide 73 text

There's no such thing as Good Code Hypothesis:

Slide 74

Slide 74 text

Snake oil still sells out as fast as Hacker News can stock it Exhibit A:

Slide 75

Slide 75 text

Projects rarely succeed or fail because of code quality Exhibit B:

Slide 76

Slide 76 text

The industry doesn't seem to produce better code over time Exhibit C:

Slide 77

Slide 77 text

If natural selection applies to software, it isn't selecting for code quality

Slide 78

Slide 78 text

No content

Slide 79

Slide 79 text

Good Code

Slide 80

Slide 80 text

1. Performs a function

Slide 81

Slide 81 text

1. Performs a function 2. Communicates intent

Slide 82

Slide 82 text

Performs a function

Slide 83

Slide 83 text

Performs a function &

Slide 84

Slide 84 text

Performs a function & ⏳

Slide 85

Slide 85 text

Performs a function & ⏳ (

Slide 86

Slide 86 text

Functionality is Objective

Slide 87

Slide 87 text

Functionality is Objective ) :ok hand sign:

Slide 88

Slide 88 text

Communicates intent

Slide 89

Slide 89 text

Communicates intent *

Slide 90

Slide 90 text

Communicates intent * +

Slide 91

Slide 91 text

Communicates intent * + ,

Slide 92

Slide 92 text

Communication is Subjective

Slide 93

Slide 93 text

Communication is Subjective - :flushed face:

Slide 94

Slide 94 text

Conflating objective & subjective goals makes evaluation hard

Slide 95

Slide 95 text

Conflating objective & subjective goals makes evaluation hard . :artist palette:

Slide 96

Slide 96 text

No content

Slide 97

Slide 97 text

No Idea

Slide 98

Slide 98 text

Otherwise, we emphasize function because measurement is easier

Slide 99

Slide 99 text

Otherwise, we emphasize function because measurement is easier / :chart with upwards trend:

Slide 100

Slide 100 text

No Idea Wrong Idea

Slide 101

Slide 101 text

Snowball Effect 0 0000 0000000 00000000 00000000 11111 1111111 2

Slide 102

Slide 102 text

As individuals 0

Slide 103

Slide 103 text

If only an app could tell us whether our code was good!

Slide 104

Slide 104 text

So I made one for you:

Slide 105

Slide 105 text

So I made one for you: is my code good.com

Slide 106

Slide 106 text

(video)

Slide 107

Slide 107 text

✅

Slide 108

Slide 108 text

(Don't view the source)

Slide 109

Slide 109 text

Version 2 Announcement:

Slide 110

Slide 110 text

Version 2 Announcement: 10x developer conversion

Slide 111

Slide 111 text

Version 2 Announcement: 10x developer conversion 4 4

Slide 112

Slide 112 text

Why do scoring, ranking & achievements comfort us? Q:

Slide 113

Slide 113 text

Quantified measurement can soothe our self-doubt Why do scoring, ranking & achievements comfort us? Q: A:

Slide 114

Slide 114 text

Every programmer shares a secret fear

Slide 115

Slide 115 text

What if my code sucks? 5

Slide 116

Slide 116 text

Everyone else seems to have it figured out… 5

Slide 117

Slide 117 text

Maybe they know something I don't? 5

Slide 118

Slide 118 text

Maybe I'll fool them if I use more big words 5

Slide 119

Slide 119 text

[coping intensifies] 5

Slide 120

Slide 120 text

[coping intensifies] 5

Slide 121

Slide 121 text

Fear, insecurity, & doubt varies 5

Slide 122

Slide 122 text

Fear, insecurity, & doubt varies 5 6

Slide 123

Slide 123 text

Fear, insecurity, & doubt varies 5 6 7

Slide 124

Slide 124 text

Fear, insecurity, & doubt varies introspective self-assured

Slide 125

Slide 125 text

Fear, insecurity, & doubt varies introspective empathetic indifferent self-assured

Slide 126

Slide 126 text

Fear, insecurity, & doubt varies introspective persuadable unflinching empathetic indifferent self-assured

Slide 127

Slide 127 text

Let's practice rating me!

Slide 128

Slide 128 text

FORM APPROVED OMB NO. 1651-0009 Customs Declaration 19 CFR 122.27, 148.12, 148.13, 148.110,148.111, 1498; 31 CFR 5316 Each arriving traveler or responsible family member must provide the following information (only ONE written declaration per family is required). The term “family” is defined as “members of a family residing in the same household who are related by blood, marriage, domestic relationship, or adoption.” 1 Family Name First (Given) Middle 8 Countries visited on this trip prior to U.S. arrival 4 (a) U.S. Street Address (hotel name/destination (b) City (c) State 10 The primary purpose of this trip is business: Yes No 11 I am (We are) bringing (a) fruits, vegetables, plants, seeds, food, insects: Yes No (b) meats, animals, animal/wildlife products: Yes No (c) disease agents, cell cultures, snails: Yes No (d) soil or have been on a farm/ranch/pasture: Yes No 12 I have (We have) been in close proximity of livestock: Yes No 3 Number of Family members traveling with you 5 Passport issued by (country) 6 Passport number 7 Country of Residence 2 Birth date Month Day Year 9 Airline/Flight No. or Vessel Name This Space For Offical Use Only

Slide 129

Slide 129 text

8 Countries visited on this trip prior to U.S. arrival 10 The primary purpose of this trip is business: Yes No 11 I am (We are) bringing (a) fruits, vegetables, plants, seeds, food, insects: Yes No (b) meats, animals, animal/wildlife products: Yes No (c) disease agents, cell cultures, snails: Yes No (d) soil or have been on a farm/ranch/pasture: Yes No 12 I have (We have) been in close proximity of livestock: Yes No (such as touching or handling) 13 I am (We are) carrying currency or monetary instruments over $10,000 U.S. or foreign equivalent: Yes No (see definition of monetary instruments on reverse) 9 Airline/Flight No. or Vessel Name

Slide 130

Slide 130 text

No content

Slide 131

Slide 131 text

No content

Slide 132

Slide 132 text

No content

Slide 133

Slide 133 text

Fear, insecurity, & doubt varies introspective self-assured

Slide 134

Slide 134 text

Fear, insecurity, & doubt varies introspective self-assured 6

Slide 135

Slide 135 text

Held to subjective evaluation standards

Slide 136

Slide 136 text

Held to subjective evaluation standards paralyzed by self-doubt

Slide 137

Slide 137 text

Held to subjective evaluation standards paralyzed by self-doubt rates self favorably

Slide 138

Slide 138 text

Communication competence:

Slide 139

Slide 139 text

Communication competence: effective communicator

Slide 140

Slide 140 text

Communication competence: effective communicator clear communicator

Slide 141

Slide 141 text

Communication competence: effective communicator clear communicator (to like-minded people)

Slide 142

Slide 142 text

we evaluate code poorly

Slide 143

Slide 143 text

we evaluate code poorly conscientious coders doubt themselves

Slide 144

Slide 144 text

we evaluate code poorly conscientious coders doubt themselves callous coders outperform others

Slide 145

Slide 145 text

we evaluate code poorly conscientious coders doubt themselves callous coders outperform others conscientious coders marginalized and then quit

Slide 146

Slide 146 text

we evaluate code poorly conscientious coders doubt themselves callous coders outperform others conscientious coders marginalized and then quit more ^

Slide 147

Slide 147 text

we evaluate code poorly conscientious coders doubt themselves callous coders outperform others conscientious coders marginalized and then quit 5 7 5 5 5 7 7 7 7 7 more ^

Slide 148

Slide 148 text

we evaluate code poorly conscientious coders doubt themselves callous coders outperform others conscientious coders marginalized and then quit 5 7 5 5 5 7 7 7 7 7 more ^

Slide 149

Slide 149 text

Guess which group does better at whiteboard interviews?

Slide 150

Slide 150 text

Guess which group does better at whiteboard interviews? NOOOOOOPE

Slide 151

Slide 151 text

Did you groan in realization this was a soft talk?

Slide 152

Slide 152 text

Then this talk's for you! Did you groan in realization this was a soft talk?

Slide 153

Slide 153 text

THE FOLLOWING TALK HAS BEEN APPROVED FOR APPROPRIATE AUDIENCES BY THE PEOPLE WHO RATE TALKS, I GUESS? THE TALK ADVERTISED HAS BEEN RATED F FEELS SOME STRONG EMOTIONS, EVIDENCE OF RELATABLE HUMANITY THROUGHOUT

Slide 154

Slide 154 text

Slide 155

Slide 155 text

Write Code the Right Way

Slide 156

Slide 156 text

Communication can only be "correct" for a set of contexts

Slide 157

Slide 157 text

XP System Metaphors

Slide 158

Slide 158 text

Mystery Men Code

Slide 159

Slide 159 text

No content

Slide 160

Slide 160 text

ಠ_ಠ

Slide 161

Slide 161 text

Know your audience

Slide 162

Slide 162 text

Know your audience , :crystal ball:

Slide 163

Slide 163 text

Popular belief in a "Right Way" causes problems

Slide 164

Slide 164 text

As a programmer, I want to convert _____ and send it over ______ using _____ so that I can ______________.

Slide 165

Slide 165 text

As a programmer, I want to convert _____ and send it over ______ using _____ so that I can ______________. to PDF

Slide 166

Slide 166 text

As a programmer, I want to convert _____ and send it over ______ using _____ so that I can ______________. Fax to PDF

Slide 167

Slide 167 text

As a programmer, I want to convert _____ and send it over ______ using _____ so that I can ______________. Fax to PDF Rails

Slide 168

Slide 168 text

As a programmer, I want to convert _____ and send it over ______ using _____ so that I can ______________. Fax to PDF Rails remain employed

Slide 169

Slide 169 text

8 best pdf gem rails

Slide 170

Slide 170 text

8 best fax gem rails

Slide 171

Slide 171 text

9 no results found

Slide 172

Slide 172 text

9 no results found : :anguished face:

Slide 173

Slide 173 text

Why would anyone prefer JavaScript?

Slide 174

Slide 174 text

What's the right way to ⛄? 5

Slide 175

Slide 175 text

What's the right way to ⛄? 5 Does your code run? If so, then that's the right way! 7

Slide 176

Slide 176 text

A Wild West can be liberating!

Slide 177

Slide 177 text

A Wild West can be liberating!

Slide 178

Slide 178 text

No content

Slide 179

Slide 179 text

0 0000 0000000 00000000 00000000 11111 1111111 2

Slide 180

Slide 180 text

As teams 00000

Slide 181

Slide 181 text

Ever excitedly try a new approach and team members shot you down?

Slide 182

Slide 182 text

Ever excitedly try a new approach and team members shot you down? < :pensive face:

Slide 183

Slide 183 text

Ever had a team member shoehorn a weird code style into your project?

Slide 184

Slide 184 text

Ever had a team member shoehorn a weird code style into your project? = :unamused face:

Slide 185

Slide 185 text

2 sides of the same coin:

Slide 186

Slide 186 text

2 sides of the same coin: Fundamental Attribution Error

Slide 187

Slide 187 text

❤ Empathy!

Slide 188

Slide 188 text

We expend emotional energy compensating for our insecurity

Slide 189

Slide 189 text

❤

Slide 190

Slide 190 text

❤

Slide 191

Slide 191 text

❤

Slide 192

Slide 192 text

Familiar Novel

Slide 193

Slide 193 text

Familiar Novel ?

Slide 194

Slide 194 text

Proven Approach Hacker News Driven Development ?

Slide 195

Slide 195 text

Proven Approach Hacker News Driven Development @

Slide 196

Slide 196 text

Stubborn and outmoded Modern Development @

Slide 197

Slide 197 text

Personal insecurity is a barrier to bridging these divides

Slide 198

Slide 198 text

Culture Fit

Slide 199

Slide 199 text

"Culture Fit"

Slide 200

Slide 200 text

No content

Slide 201

Slide 201 text

"Culture" vs. "Monoculture"

Slide 202

Slide 202 text

Dirty Secret #1:

Slide 203

Slide 203 text

Dirty Secret #1: Monocultures work faster!

Slide 204

Slide 204 text

Proven Approach Hacker News Driven Development ?

Slide 205

Slide 205 text

Proven Approach Hacker News Driven Development ?? ? ? ? ?

Slide 206

Slide 206 text

"Meritocracies" incidentally reinforce monocultures

Slide 207

Slide 207 text

?? ? ? ? ?

Slide 208

Slide 208 text

?? ? ? ? ? A

Slide 209

Slide 209 text

Dirty Secret #2:

Slide 210

Slide 210 text

Dirty Secret #2: faster != better

Slide 211

Slide 211 text

The world teaches us that slow == stupid

Slide 212

Slide 212 text

Teams that overcome differing perspectives are slower

Slide 213

Slide 213 text

Teams that overcome differing perspectives are slower*

Slide 214

Slide 214 text

Teams that overcome differing perspectives are slower *but write more robust systems *

Slide 215

Slide 215 text

Proven Approach ?? ? Modern Development @@ @

Slide 216

Slide 216 text

B Please! Stop Claiming B

Slide 217

Slide 217 text

"trust us, is faster in the long run!" B Please! Stop Claiming B

Slide 218

Slide 218 text

Dirty Secret #3

Slide 219

Slide 219 text

Dirty Secret #3 Most dichotomies are false

Slide 220

Slide 220 text

? @

Slide 221

Slide 221 text

? C D @ E F

Slide 222

Slide 222 text

Culture Fit ? D E

Slide 223

Slide 223 text

Culture Fit ? D E +

Slide 224

Slide 224 text

What about code? G

Slide 225

Slide 225 text

No content

Slide 226

Slide 226 text

Functionality

Slide 227

Slide 227 text

Functionality Communication

Slide 228

Slide 228 text

Functionality Communication

Slide 229

Slide 229 text

Priorities functionality communication

Slide 230

Slide 230 text

Priorities functionality communicate to humans

Slide 231

Slide 231 text

Priorities communicate to computers communicate to humans

Slide 232

Slide 232 text

Priorities communicate to computers H communicate to humans

Slide 233

Slide 233 text

I Priorities communicate to computers communicate to humans

Slide 234

Slide 234 text

Priorities J communicate to computers communicate to humans

Slide 235

Slide 235 text

K Priorities communicate to computers communicate to humans

Slide 236

Slide 236 text

$ Priorities communicate to computers communicate to humans

Slide 237

Slide 237 text

Functionality Communication

Slide 238

Slide 238 text

Functionality Communication

Slide 239

Slide 239 text

How is our code communicating?

Slide 240

Slide 240 text

We don't have a good vocabulary for this yet

Slide 241

Slide 241 text

Indirection Analysis

Slide 242

Slide 242 text

Each {lib, file, method, name} is an indirection

Slide 243

Slide 243 text

Each {macro, reflection, metaprogram} is a SUPER indirection

Slide 244

Slide 244 text

Indirection Score For a given code path:

Slide 245

Slide 245 text

Indirection Score For a given code path: 1. How many names are encountered?

Slide 246

Slide 246 text

Indirection Score For a given code path: 1. How many names are encountered? 2. How many source files contribute code?

Slide 247

Slide 247 text

Indirection Score For a given code path: 1. How many names are encountered? 2. How many source files contribute code? 3. How many tests redundantly cover it?

Slide 248

Slide 248 text

Indirection Score For a given code path: 1. How many names are encountered? 2. How many source files contribute code? 3. How many tests redundantly cover it? 4. How much is handled by dependencies?

Slide 249

Slide 249 text

WET DRY Indirection

Slide 250

Slide 250 text

WET Duplicate Nothing Indirection

Slide 251

Slide 251 text

Couple Nothing Duplicate Nothing Indirection

Slide 252

Slide 252 text

Couple Nothing Duplicate Nothing

Slide 253

Slide 253 text

Couple Nothing Duplicate Nothing Both extremes are costly

Slide 254

Slide 254 text

Couple Nothing Duplicate Nothing

Slide 255

Slide 255 text

Couple Nothing Duplicate Nothing E change one thing

Slide 256

Slide 256 text

Couple Nothing Duplicate Nothing E change one thing L change many things

Slide 257

Slide 257 text

Couple Nothing Duplicate Nothing

Slide 258

Slide 258 text

Couple Nothing Duplicate Nothing E change many things

Slide 259

Slide 259 text

Couple Nothing Duplicate Nothing E change many things L change one thing

Slide 260

Slide 260 text

Couple Nothing Duplicate Nothing

Slide 261

Slide 261 text

Couple Nothing Duplicate Nothing E learn one piece

Slide 262

Slide 262 text

Couple Nothing Duplicate Nothing E learn one piece L learn entire system

Slide 263

Slide 263 text

Couple Nothing Duplicate Nothing

Slide 264

Slide 264 text

Couple Nothing Duplicate Nothing L learn one piece

Slide 265

Slide 265 text

Couple Nothing Duplicate Nothing L learn one piece E learn entire system

Slide 266

Slide 266 text

Couple Nothing Duplicate Nothing

Slide 267

Slide 267 text

Couple Nothing Duplicate Nothing Yay Nuance!

Slide 268

Slide 268 text

Explicit vs. Implicit Indirection

Slide 269

Slide 269 text

Explicit vs. Implicit Indirection ❄

Slide 270

Slide 270 text

Explicit vs. Implicit Indirection ❄ N

Slide 271

Slide 271 text

Practice communicating about our code's communication

Slide 272

Slide 272 text

#thoughtleadering opportunities abound!

Slide 273

Slide 273 text

0 0000 0000000 00000000 00000000 11111 1111111 2

Slide 274

Slide 274 text

As a community 0000000000000000 0000000000000000 0000000000000000

Slide 275

Slide 275 text

Your team's 6th person

Slide 276

Slide 276 text

Your team's 6th person ?

Slide 277

Slide 277 text

Your team's 6th person ?

Slide 278

Slide 278 text

Your team's 6th person ?

Slide 279

Slide 279 text

Your team's 6th person ?

Slide 280

Slide 280 text

Thought Leaders O

Slide 281

Slide 281 text

Thought Leaders O PQ

Slide 282

Slide 282 text

Thought Leaders O PQ R

Slide 283

Slide 283 text

Who does our code talk to?

Slide 284

Slide 284 text

No content

Slide 285

Slide 285 text

No content

Slide 286

Slide 286 text

Slide 287

Slide 287 text

Slide 288

Slide 288 text

Slide 289

Slide 289 text

S :face with cold sweat:

Slide 290

Slide 290 text

No content

Slide 291

Slide 291 text

No content

Slide 292

Slide 292 text

Slide 293

Slide 293 text

T :disappointed but relieved face:

Slide 294

Slide 294 text

No content

Slide 295

Slide 295 text

Slide 296

Slide 296 text

7 7

Slide 297

Slide 297 text

Hero Worship

Slide 298

Slide 298 text

No content

Slide 299

Slide 299 text

No content

Slide 300

Slide 300 text

No content

Slide 301

Slide 301 text

Now that I'm a Certified Keynote Speaker™

Slide 302

Slide 302 text

Now that I'm a Certified Keynote Speaker™ [shuddering intensifies]

Slide 303

Slide 303 text

Your clever code does not impress me

Slide 304

Slide 304 text

Your clever code makes me feel stupid

Slide 305

Slide 305 text

Clever code is a symptom of poor understanding

Slide 306

Slide 306 text

No content

Slide 307

Slide 307 text

Obvious is more impressive than clever

Slide 308

Slide 308 text

Code design approaches are memes

Slide 309

Slide 309 text

Code design approaches are memes MVC

Slide 310

Slide 310 text

Code design approaches are memes MVC BDD

Slide 311

Slide 311 text

Code design approaches are memes MVC BDD DSLs

Slide 312

Slide 312 text

Code design approaches are memes MVC BDD View Presenters DSLs

Slide 313

Slide 313 text

Code design approaches are memes MVC BDD Fast Specs View Presenters DSLs

Slide 314

Slide 314 text

Code design approaches are memes MVC BDD Fast Specs View Presenters Hexagonal Rails DSLs

Slide 315

Slide 315 text

Code design approaches are memes MVC BDD Fast Specs View Presenters Hexagonal Rails DSLs DCI

Slide 316

Slide 316 text

Code design approaches are memes MVC BDD Fast Specs View Presenters Hexagonal Rails DSLs DCI Fat models / Skinny controllers

Slide 317

Slide 317 text

Memes are ideas competing for attention via natural selection

Slide 318

Slide 318 text

Slide 319

Slide 319 text

Somebody has idea 0 U

Slide 320

Slide 320 text

Somebody has idea 0 Experiments with idea 0 U

Slide 321

Slide 321 text

Somebody has idea 0 Experiments with idea 0 Shares idea with others 00 U

Slide 322

Slide 322 text

Somebody has idea 0 Experiments with idea 0 Shares idea with others 00 Idea becomes popular 000 U

Slide 323

Slide 323 text

Somebody has idea 0 Experiments with idea 0 Shares idea with others 00 Idea becomes popular 000 Idea becomes ubiquitous 0000 U

Slide 324

Slide 324 text

Somebody has idea 0 Experiments with idea 0 Shares idea with others 00 Idea becomes popular 000 Idea becomes ubiquitous 0000 Idea is finally worth using U

Slide 325

Slide 325 text

Somebody has idea 0 Experiments with idea 0 Shares idea with others 00 Idea becomes popular 000 Idea becomes ubiquitous 0000 Idea is finally worth using V⁉ U

Slide 326

Slide 326 text

Memes are most valuable when our audience knows them

Slide 327

Slide 327 text

How do design memes ever become ubiquitous?! Q:

Slide 328

Slide 328 text

Symbiotic relationships with early adopters who oversell any intrinsic benefits! How do design memes ever become ubiquitous?! Q: A:

Slide 329

Slide 329 text

Somebody has idea U 0 Experiments with idea 0 Idea becomes popular 000 Idea becomes ubiquitous 0000 Idea is finally worth using V⁉ Shares idea with others 00

Slide 330

Slide 330 text

Somebody has idea U 0 Experiments with idea 0 Idea becomes popular 000 Idea becomes ubiquitous 0000 Idea is finally worth using V⁉ Shares idea with others 00

Slide 331

Slide 331 text

Somebody has idea U 0 Experiments with idea 0 Idea becomes popular 000 Idea becomes ubiquitous 0000 Idea is finally worth using V⁉ Shares idea with others 00 "Evangelists"

Slide 332

Slide 332 text

Somebody has idea U 0 Experiments with idea 0 Idea becomes popular 000 Idea becomes ubiquitous 0000 Idea is finally worth using V⁉ Shares idea with others 00 Meme Salespeople

Slide 333

Slide 333 text

Shares idea with others 00 Somebody has idea U 0 Experiments with idea 0 Idea becomes ubiquitous 0000 Idea is finally worth using V⁉ Idea becomes popular 000

Slide 334

Slide 334 text

Shares idea with others 00 Somebody has idea U 0 Experiments with idea 0 Idea becomes ubiquitous 0000 Idea is finally worth using V⁉ Idea becomes popular 000 Aspirational Adopters

Slide 335

Slide 335 text

Everyone wants their meme to reach ubiquity & may pressure you to adopt it

Slide 336

Slide 336 text

Know your audience , :crystal ball:

Slide 337

Slide 337 text

0 0000 0000000 00000000 00000000 11111 1111111 2

Slide 338

Slide 338 text

0 0000 0000000 00000000 00000000 11111 1111111 2

Slide 339

Slide 339 text

As an industry 111111111111111 111111111111111 111111111111111

Slide 340

Slide 340 text

As an industry 1111111X1111111 111X11111111111 1X11111111X1111

Slide 341

Slide 341 text

You think our inability to evaluate code makes us uncomfortable?

Slide 342

Slide 342 text

You think our inability to evaluate code makes us uncomfortable? Try talking to a businessperson!

Slide 343

Slide 343 text

No content

Slide 344

Slide 344 text

How can a non-technical person be sure they're hiring good developers?

Slide 345

Slide 345 text

How can a non-technical person be sure they're hiring good developers? Y

Slide 346

Slide 346 text

How can a non-technical person be sure they're hiring good developers? Y Z

Slide 347

Slide 347 text

Request for Proposals

Slide 348

Slide 348 text

5 @

Slide 349

Slide 349 text

5 @

Slide 350

Slide 350 text

5 @ - Identifies risk, assumptions

Slide 351

Slide 351 text

5 @ - Identifies risk, assumptions - Rationalizes away risk

Slide 352

Slide 352 text

5 @ - Identifies risk, assumptions - Emphasizes collaboration - Rationalizes away risk

Slide 353

Slide 353 text

5 @ - Identifies risk, assumptions - Emphasizes collaboration - Rationalizes away risk - Emphasizes competence

Slide 354

Slide 354 text

5 @ - Identifies risk, assumptions - Emphasizes collaboration - Estimates pessimistically - Rationalizes away risk - Emphasizes competence

Slide 355

Slide 355 text

5 @ - Identifies risk, assumptions - Emphasizes collaboration - Estimates pessimistically - Rationalizes away risk - Emphasizes competence - Estimates optimistically

Slide 356

Slide 356 text

5 @ - Identifies risk, assumptions - Emphasizes collaboration - Estimates pessimistically - Higher bid, rarely wins - Rationalizes away risk - Emphasizes competence - Estimates optimistically

Slide 357

Slide 357 text

5 @ - Identifies risk, assumptions - Emphasizes collaboration - Estimates pessimistically - Higher bid, rarely wins - Rationalizes away risk - Emphasizes competence - Estimates optimistically - Lower bid, often wins

Slide 358

Slide 358 text

5 @ - Identifies risk, assumptions - Emphasizes collaboration - Estimates pessimistically - Higher bid, rarely wins - Blames failures on self - Rationalizes away risk - Emphasizes competence - Estimates optimistically - Lower bid, often wins

Slide 359

Slide 359 text

Slide 360

Slide 360 text

Businesses don't realize asking for proposals biases their decisions

Slide 361

Slide 361 text

Comforting myths that code is {tangible,quantifiable,fungible} only perpetuate this bias

Slide 362

Slide 362 text

Instead, why not admit & educate that software is full of uncertainty?

Slide 363

Slide 363 text

B Construction [

Slide 364

Slide 364 text

B Construction [ vs

Slide 365

Slide 365 text

B Construction [ vs \ Surgery ✂

Slide 366

Slide 366 text

B Construction [ vs \ Surgery ✂ (metaphor credit: Dan North)

Slide 367

Slide 367 text

E Estimates! E

Slide 368

Slide 368 text

E Estimates! E How much time will it take to build with Good Code™?

Slide 369

Slide 369 text

E Estimates! E How much time will it take to build with Good Code™? vs

Slide 370

Slide 370 text

E Estimates! E How much time will it take to build with Good Code™? How much uncertainty and/or risk does it pose? vs

Slide 371

Slide 371 text

+ Estimates! +

Slide 372

Slide 372 text

+ Estimates! + How bad of my Good Code™ will you accept?

Slide 373

Slide 373 text

+ Estimates! + How bad of my Good Code™ will you accept? vs

Slide 374

Slide 374 text

+ Estimates! + How bad of my Good Code™ will you accept? vs How much uncertainty will you tolerate?

Slide 375

Slide 375 text

Pick the most uncertain feature

Slide 376

Slide 376 text

Pick the most uncertain feature Identify risks & unknowns

Slide 377

Slide 377 text

Pick the most uncertain feature Identify risks & unknowns Execute spikes to reduce uncertainty

Slide 378

Slide 378 text

Pick the most uncertain feature Identify risks & unknowns Execute spikes to reduce uncertainty Implement with boring code

Slide 379

Slide 379 text

Pick the most uncertain feature Identify risks & unknowns Execute spikes to reduce uncertainty Implement with boring code

Slide 380

Slide 380 text

Pick the most uncertain feature Identify risks & unknowns Execute spikes to reduce uncertainty Implement with boring code The Boring Code Discovery Model

Slide 381

Slide 381 text

Pick the most uncertain feature Identify risks & unknowns Execute spikes to reduce uncertainty Implement with boring code The Boring Code Discovery Model Certification Program Coming Soon!

Slide 382

Slide 382 text

How will we know boring code when we see it?

Slide 383

Slide 383 text

What even is boring code?

Slide 384

Slide 384 text

Shared Context Enough What even is boring code?

Slide 385

Slide 385 text

Shared Context Technical Concepts Minimal Enough + What even is boring code?

Slide 386

Slide 386 text

Shared Context Technical Concepts Domain Concepts Minimal Clear Enough + + What even is boring code?

Slide 387

Slide 387 text

Shared Context Technical Concepts Domain Concepts Empathy Minimal Clear Lots of Enough + + + What even is boring code?

Slide 388

Slide 388 text

Shared Context Technical Concepts Domain Concepts Empathy

Slide 389

Slide 389 text

Shared Context Technical Concepts Domain Concepts Empathy

Slide 390

Slide 390 text

Shared Context Technical Concepts Domain Concepts Empathy An Omakase Rails Project

Slide 391

Slide 391 text

Shared Context Technical Concepts Domain Concepts Empathy A Prime Rails Project

Slide 392

Slide 392 text

Shared Context Technical Concepts Domain Concepts Empathy A Node.js Project

Slide 393

Slide 393 text

Shared Context Technical Concepts Domain Concepts Empathy A Java Project

Slide 394

Slide 394 text

Shared Context Technical Concepts Domain Concepts Empathy An Ember.js Project

Slide 395

Slide 395 text

¯\_(π)_/¯

Slide 396

Slide 396 text

#ymmv ¯\_(π)_/¯

Slide 397

Slide 397 text

What can we start ☀ doing tomorrow? ☀

Slide 398

Slide 398 text

Relax your conception of universally Good Code™

Slide 399

Slide 399 text

How we evaluate code is subjective and flawed

Slide 400

Slide 400 text

How we evaluate code is subjective and flawed …so fearing your code sucks is both natural and pointless

Slide 401

Slide 401 text

Claiming a Right Way™ may push others away

Slide 402

Slide 402 text

Seek opportunities to deliberate Kindly and Respectfully with people who think differently

Slide 403

Slide 403 text

Whenever you see the word 'clever', substitute it with 'self-indulgent'.

Slide 404

Slide 404 text

Whenever you see the word 'clever', substitute it with 'self-indulgent'. ~ Don Norman

Slide 405

Slide 405 text

Metaphors & memes are powerful but limit your audience to whoever understands them

Slide 406

Slide 406 text

When someone doesn't understand your code, assume some responsibility

Slide 407

Slide 407 text

Kip Thorne, The Science of Interstellar:

Slide 408

Slide 408 text

“Some segments of this book may be rough going. That’s the nature of real science. It requires thought. Sometimes deep thought. But thinking can be rewarding. You can just skip the rough parts, or you can struggle to understand. If your struggle is fruitless, then that’s my fault, not yours, and I apologize." Kip Thorne, The Science of Interstellar: