Sometimes a Controller is Just a Controller

As presented at RailsConf 2015. Video: http://blog.testdouble.com/posts/2015-05-11-sometimes-a-controller-is-just-a-controller.html

Transcript

2. Fancy Code
3. vs Fancy Code
4. boring code vs Fancy Code
8. Boring code is so much easier to read!
9. Turns out, that'd be a boring talk
10. Slides
12. I am not an artiste
13. I am not an artiste
14. I am not an artíste
15. I am not an artìste
16. Artists say "I love your slides"
17. Artists say "I love your slides" ! :crying with tears of joy:
18. "Really, I love that you put so much time into your slides"
19. "Really, I love that you put so much time into your slides" " :loudly crying face:
20. Time
21. Time ⏰
22. Time
24. Horological Study:
25. Horological Study: time -slides= 0
26. People Won Over
27. 0% 20% 40% 60% 80% 100% 1 hour 10 hours 20 hours 40 hours 60 hours People Won Over
28. 0% 20% 40% 60% 80% 100% 1 hour 10 hours 20 hours 40 hours 60 hours People Won Over
29. 0% 20% 40% 60% 80% 100% 1 hour 10 hours 20 hours 40 hours 60 hours People Won Over
30. 0% 20% 40% 60% 80% 100% 1 hour 10 hours 20 hours 40 hours 60 hours People Won Over
31. 0% 20% 40% 60% 80% 100% 1 hour 10 hours 20 hours 40 hours 60 hours People Won Over
32. 0% 20% 40% 60% 80% 100% 1 hour 10 hours 20 hours 40 hours 60 hours People Won Over
33. 0% 20% 40% 60% 80% 100% 1 hour 10 hours 20 hours 40 hours 60 hours People Won Over X
34. 0% 20% 40% 60% 80% 100% 1 hour 10 hours 20 hours 40 hours 60 hours People Won Over X
35. 80 / 20 Rule
36. 0% 20% 40% 60% 80% 100% 1 hour 10 hours 20 hours 40 hours 60 hours People Won Over X
37. 0% 20% 40% 60% 80% 100% 1 hour 10 hours 20 hours 40 hours 60 hours People Won Over X
38. Time ⏰
40. Sometimes a slide is just a slide
41. "Good" Talk
42. But anyway
43. Good Code
44. 1. tiny units
45. 1. tiny units 1a. no, like hilariously tiny
46. 1. tiny units 1a. no, like hilariously tiny 1b. as in, units with one public method
47. 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
48. 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
49. 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
50. 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
51. 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
52. 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
53. 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!"
54. 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
55. 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 6. pull side-effects nearer the entry point (imperative shell / functional core)
56. 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 6. pull side-effects nearer the entry point (imperative shell / functional core) 7. disagree with whatever my pair does every 10 minutes
57. 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 6. pull side-effects nearer the entry point (imperative shell / functional core) 7. disagree with whatever my pair does every 10 minutes 8. overwhelm people with information so that I get my way
58. The end.
59. My name is Justin Searls
    Please tweet me @searls &
    Say hello@testdouble.com
60. ( ͠° ͟ʖ ͡°)
61. ( ͡~ ͜ ʖ ͡°)
62. My Favorite Way
63. Your Favorite Way
64. Your Team's Favorite Way
65. Your Framework's Favorite Way
66. Your Boss's Favorite Way
67. Your Boss's Favorite Way $
68. Your Boss's Favorite Way ⏰ $
69. Your Boss's Favorite Way % ⏰ $
70. Text (video)
71. If you combine everybody's favorite way then maybe…
72. Good Code
73. There's no such thing as Good Code Hypothesis:
74. Snake oil still sells out as fast as Hacker News can stock it Exhibit A:
75. Projects rarely succeed or fail because of code quality Exhibit B:
76. The industry doesn't seem to produce better code over time Exhibit C:
77. If natural selection applies to software, it isn't selecting for code quality
79. Good Code
80. 1. Performs a function
81. 1. Performs a function 2. Communicates intent
82. Performs a function
83. Performs a function &
84. Performs a function & ⏳
85. Performs a function & ⏳ (
86. Functionality is Objective
87. Functionality is Objective ) :ok hand sign:
88. Communicates intent
89. Communicates intent *
90. Communicates intent * +
91. Communicates intent * + ,
92. Communication is Subjective
93. Communication is Subjective - :flushed face:
94. Conflating objective & subjective goals makes evaluation hard
95. Conflating objective & subjective goals makes evaluation hard . :artist palette:
97. No Idea
98. Otherwise, we emphasize function because measurement is easier
99. Otherwise, we emphasize function because measurement is easier / :chart with upwards trend:
100. No Idea Wrong Idea
101. Snowball Effect 0 0000 0000000 00000000 00000000 11111 1111111 2
102. As individuals 0
103. If only an app could tell us whether our code was good!
104. So I made one for you:
105. So I made one for you: is my code good.com
106. (video)
107. ✅
108. (Don't view the source)
109. Version 2 Announcement:
110. Version 2 Announcement: 10x developer conversion
111. Version 2 Announcement: 10x developer conversion 4 4
112. Why do scoring, ranking & achievements comfort us? Q:
113. Quantified measurement can soothe our self-doubt Why do scoring, ranking & achievements comfort us? Q: A:
114. Every programmer shares a secret fear
115. What if my code sucks? 5
116. Everyone else seems to have it figured out… 5
117. Maybe they know something I don't? 5
118. Maybe I'll fool them if I use more big words 5
119. [coping intensifies] 5
120. [coping intensifies] 5
121. Fear, insecurity, & doubt varies 5
122. Fear, insecurity, & doubt varies 5 6
123. Fear, insecurity, & doubt varies 5 6 7
124. Fear, insecurity, & doubt varies introspective self-assured
125. Fear, insecurity, & doubt varies introspective empathetic indifferent self-assured
126. Fear, insecurity, & doubt varies introspective persuadable unflinching empathetic indifferent self-assured
127. Let's practice rating me!
128. 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
129. 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
133. Fear, insecurity, & doubt varies introspective self-assured
134. Fear, insecurity, & doubt varies introspective self-assured 6
135. Held to subjective evaluation standards
136. Held to subjective evaluation standards paralyzed by self-doubt
137. Held to subjective evaluation standards paralyzed by self-doubt rates self favorably
138. Communication competence:
139. Communication competence: effective communicator
140. Communication competence: effective communicator clear communicator
141. Communication competence: effective communicator clear communicator (to like-minded people)
142. we evaluate code poorly
143. we evaluate code poorly conscientious coders doubt themselves
144. we evaluate code poorly conscientious coders doubt themselves callous coders outperform others
145. we evaluate code poorly conscientious coders doubt themselves callous coders outperform others conscientious coders marginalized and then quit
146. we evaluate code poorly conscientious coders doubt themselves callous coders outperform others conscientious coders marginalized and then quit more ^
147. 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 ^
148. 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 ^
149. Guess which group does better at whiteboard interviews?
150. Guess which group does better at whiteboard interviews? NOOOOOOPE
151. Did you groan in realization this was a soft talk?
152. Then this talk's for you! Did you groan in realization this was a soft talk?
153. 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
154. 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
155. Write Code the Right Way
156. Communication can only be "correct" for a set of contexts
157. XP System Metaphors
158. Mystery Men Code
160. ಠ_ಠ
161. Know your audience
162. Know your audience , :crystal ball:
163. Popular belief in a "Right Way" causes problems
164. As a programmer, I want to convert _____ and send it over ______ using _____ so that I can ______________.
165. As a programmer, I want to convert _____ and send it over ______ using _____ so that I can ______________. to PDF
166. As a programmer, I want to convert _____ and send it over ______ using _____ so that I can ______________. Fax to PDF
167. As a programmer, I want to convert _____ and send it over ______ using _____ so that I can ______________. Fax to PDF Rails
168. As a programmer, I want to convert _____ and send it over ______ using _____ so that I can ______________. Fax to PDF Rails remain employed
169. 8 best pdf gem rails
170. 8 best fax gem rails
171. 9 no results found
172. 9 no results found : :anguished face:
173. Why would anyone prefer JavaScript?
174. What's the right way to ⛄? 5
175. What's the right way to ⛄? 5 Does your code run? If so, then that's the right way! 7
176. A Wild West can be liberating!
177. A Wild West can be liberating!
179. 0 0000 0000000 00000000 00000000 11111 1111111 2
180. As teams 00000
181. Ever excitedly try a new approach and team members shot you down?
182. Ever excitedly try a new approach and team members shot you down? < :pensive face:
183. Ever had a team member shoehorn a weird code style into your project?
184. Ever had a team member shoehorn a weird code style into your project? = :unamused face:
185. 2 sides of the same coin:
186. 2 sides of the same coin: Fundamental Attribution Error
187. ❤ Empathy!
188. We expend emotional energy compensating for our insecurity
189. ❤
190. ❤
191. ❤
192. Familiar Novel
193. Familiar Novel ?
194. Proven Approach Hacker News Driven Development ?
195. Proven Approach Hacker News Driven Development @
196. Stubborn and outmoded Modern Development @
197. Personal insecurity is a barrier to bridging these divides
198. Culture Fit
199. "Culture Fit"
201. "Culture" vs. "Monoculture"
202. Dirty Secret #1:
203. Dirty Secret #1: Monocultures work faster!
204. Proven Approach Hacker News Driven Development ?
205. Proven Approach Hacker News Driven Development ?? ? ? ? ?
206. "Meritocracies" incidentally reinforce monocultures
207. ?? ? ? ? ?
208. ?? ? ? ? ? A
209. Dirty Secret #2:
210. Dirty Secret #2: faster != better
211. The world teaches us that slow == stupid
212. Teams that overcome differing perspectives are slower
213. Teams that overcome differing perspectives are slower*
214. Teams that overcome differing perspectives are slower *but write more robust systems *
215. Proven Approach ?? ? Modern Development @@ @
216. B Please! Stop Claiming B
217. "trust us, <Some Practice> is faster in the long run!" B Please! Stop Claiming B
218. Dirty Secret #3
219. Dirty Secret #3 Most dichotomies are false
220. ? @
221. ? C D @ E F
222. Culture Fit ? D E
223. Culture Fit ? D E +
224. What about code? G
226. Functionality
227. Functionality Communication
228. Functionality Communication
229. Priorities functionality communication
230. Priorities functionality communicate to humans
231. Priorities communicate to computers communicate to humans
232. Priorities communicate to computers H communicate to humans
233. I Priorities communicate to computers communicate to humans
234. Priorities J communicate to computers communicate to humans
235. K Priorities communicate to computers communicate to humans
236. $ Priorities communicate to computers communicate to humans
237. Functionality Communication
238. Functionality Communication
239. How is our code communicating?
240. We don't have a good vocabulary for this yet
241. Indirection Analysis
242. Each {lib, file, method, name} is an indirection
243. Each {macro, reflection, metaprogram} is a SUPER indirection
244. Indirection Score For a given code path:
245. Indirection Score For a given code path: 1. How many names are encountered?
246. Indirection Score For a given code path: 1. How many names are encountered? 2. How many source files contribute code?
247. 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?
248. 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?
249. WET DRY Indirection
250. WET Duplicate Nothing Indirection
251. Couple Nothing Duplicate Nothing Indirection
252. Couple Nothing Duplicate Nothing
253. Couple Nothing Duplicate Nothing Both extremes are costly
254. Couple Nothing Duplicate Nothing
255. Couple Nothing Duplicate Nothing E change one thing
256. Couple Nothing Duplicate Nothing E change one thing L change many things
257. Couple Nothing Duplicate Nothing
258. Couple Nothing Duplicate Nothing E change many things
259. Couple Nothing Duplicate Nothing E change many things L change one thing
260. Couple Nothing Duplicate Nothing
261. Couple Nothing Duplicate Nothing E learn one piece
262. Couple Nothing Duplicate Nothing E learn one piece L learn entire system
263. Couple Nothing Duplicate Nothing
264. Couple Nothing Duplicate Nothing L learn one piece
265. Couple Nothing Duplicate Nothing L learn one piece E learn entire system
266. Couple Nothing Duplicate Nothing
267. Couple Nothing Duplicate Nothing Yay Nuance!
268. Explicit vs. Implicit Indirection
269. Explicit vs. Implicit Indirection ❄
270. Explicit vs. Implicit Indirection ❄ N
271. Practice communicating about our code's communication
272. #thoughtleadering opportunities abound!
273. 0 0000 0000000 00000000 00000000 11111 1111111 2
274. As a community 0000000000000000 0000000000000000 0000000000000000
275. Your team's 6th person
276. Your team's 6th person ?
277. Your team's 6th person ?
278. Your team's 6th person ?
279. Your team's 6th person ?
280. Thought Leaders O
281. Thought Leaders O PQ
282. Thought Leaders O PQ R
283. Who does our code talk to?
286. ?
287. ?
288. S
289. S :face with cold sweat:
292. T
293. T :disappointed but relieved face:
296. 7 7
297. Hero Worship
301. Now that I'm a Certified Keynote Speaker™
302. Now that I'm a Certified Keynote Speaker™ [shuddering intensifies]
303. Your clever code does not impress me
304. Your clever code makes me feel stupid
305. Clever code is a symptom of poor understanding
307. Obvious is more impressive than clever
308. Code design approaches are memes
309. Code design approaches are memes MVC
310. Code design approaches are memes MVC BDD
311. Code design approaches are memes MVC BDD DSLs
312. Code design approaches are memes MVC BDD View Presenters DSLs
313. Code design approaches are memes MVC BDD Fast Specs View Presenters DSLs
314. Code design approaches are memes MVC BDD Fast Specs View Presenters Hexagonal Rails DSLs
315. Code design approaches are memes MVC BDD Fast Specs View Presenters Hexagonal Rails DSLs DCI
316. Code design approaches are memes MVC BDD Fast Specs View Presenters Hexagonal Rails DSLs DCI Fat models / Skinny controllers
317. Memes are ideas competing for attention via natural selection
318. U
319. Somebody has idea 0 U
320. Somebody has idea 0 Experiments with idea 0 U
321. Somebody has idea 0 Experiments with idea 0 Shares idea with others 00 U
322. Somebody has idea 0 Experiments with idea 0 Shares idea with others 00 Idea becomes popular 000 U
323. Somebody has idea 0 Experiments with idea 0 Shares idea with others 00 Idea becomes popular 000 Idea becomes ubiquitous 0000 U
324. 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
325. 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
326. Memes are most valuable when our audience knows them
327. How do design memes ever become ubiquitous?! Q:
328. Symbiotic relationships with early adopters who oversell any intrinsic benefits! How do design memes ever become ubiquitous?! Q: A:
329. 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
330. 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
331. 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"
332. 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
333. 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
334. 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
335. Everyone wants their meme to reach ubiquity & may pressure you to adopt it
336. Know your audience , :crystal ball:
337. 0 0000 0000000 00000000 00000000 11111 1111111 2
338. 0 0000 0000000 00000000 00000000 11111 1111111 2
339. As an industry 111111111111111 111111111111111 111111111111111
340. As an industry 1111111X1111111 111X11111111111 1X11111111X1111
341. You think our inability to evaluate code makes us uncomfortable?
342. You think our inability to evaluate code makes us uncomfortable? Try talking to a businessperson!
344. How can a non-technical person be sure they're hiring good developers?
345. How can a non-technical person be sure they're hiring good developers? Y
346. How can a non-technical person be sure they're hiring good developers? Y Z
347. Request for Proposals
348. 5 @
349. 5 @
350. 5 @ - Identifies risk, assumptions
351. 5 @ - Identifies risk, assumptions - Rationalizes away risk
352. 5 @ - Identifies risk, assumptions - Emphasizes collaboration - Rationalizes away risk
353. 5 @ - Identifies risk, assumptions - Emphasizes collaboration - Rationalizes away risk - Emphasizes competence
354. 5 @ - Identifies risk, assumptions - Emphasizes collaboration - Estimates pessimistically - Rationalizes away risk - Emphasizes competence
355. 5 @ - Identifies risk, assumptions - Emphasizes collaboration - Estimates pessimistically - Rationalizes away risk - Emphasizes competence - Estimates optimistically
356. 5 @ - Identifies risk, assumptions - Emphasizes collaboration - Estimates pessimistically - Higher bid, rarely wins - Rationalizes away risk - Emphasizes competence - Estimates optimistically
357. 5 @ - Identifies risk, assumptions - Emphasizes collaboration - Estimates pessimistically - Higher bid, rarely wins - Rationalizes away risk - Emphasizes competence - Estimates optimistically - Lower bid, often wins
358. 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
359. 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 - Blames failures on others
360. Businesses don't realize asking for proposals biases their decisions
361. Comforting myths that code is {tangible,quantifiable,fungible} only perpetuate this bias
362. Instead, why not admit & educate that software is full of uncertainty?
363. B Construction [
364. B Construction [ vs
365. B Construction [ vs \ Surgery ✂
366. B Construction [ vs \ Surgery ✂ (metaphor credit: Dan North)
367. E Estimates! E
368. E Estimates! E How much time will it take to build with Good Code™?
369. E Estimates! E How much time will it take to build with Good Code™? vs
370. E Estimates! E How much time will it take to build with Good Code™? How much uncertainty and/or risk does it pose? vs
371. + Estimates! +
372. + Estimates! + How bad of my Good Code™ will you accept?
373. + Estimates! + How bad of my Good Code™ will you accept? vs
374. + Estimates! + How bad of my Good Code™ will you accept? vs How much uncertainty will you tolerate?
375. Pick the most uncertain feature
376. Pick the most uncertain feature Identify risks & unknowns
377. Pick the most uncertain feature Identify risks & unknowns Execute spikes to reduce uncertainty
378. Pick the most uncertain feature Identify risks & unknowns Execute spikes to reduce uncertainty Implement with boring code
379. Pick the most uncertain feature Identify risks & unknowns Execute spikes to reduce uncertainty Implement with boring code
380. Pick the most uncertain feature Identify risks & unknowns Execute spikes to reduce uncertainty Implement with boring code The Boring Code Discovery Model
381. 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!
382. How will we know boring code when we see it?
383. What even is boring code?
384. Shared Context Enough What even is boring code?
385. Shared Context Technical Concepts Minimal Enough + What even is boring code?
386. Shared Context Technical Concepts Domain Concepts Minimal Clear Enough + + What even is boring code?
387. Shared Context Technical Concepts Domain Concepts Empathy Minimal Clear Lots of Enough + + + What even is boring code?
388. Shared Context Technical Concepts Domain Concepts Empathy
389. Shared Context Technical Concepts Domain Concepts Empathy
390. Shared Context Technical Concepts Domain Concepts Empathy An Omakase Rails Project
391. Shared Context Technical Concepts Domain Concepts Empathy A Prime Rails Project
392. Shared Context Technical Concepts Domain Concepts Empathy A Node.js Project
393. Shared Context Technical Concepts Domain Concepts Empathy A Java Project
394. Shared Context Technical Concepts Domain Concepts Empathy An Ember.js Project
395. ¯\_(π)_/¯
396. #ymmv ¯\_(π)_/¯
397. What can we start ☀ doing tomorrow? ☀
398. Relax your conception of universally Good Code™
399. How we evaluate code is subjective and flawed
400. How we evaluate code is subjective and flawed …so fearing your code sucks is both natural and pointless
401. Claiming a Right Way™ may push others away
402. Seek opportunities to deliberate Kindly and Respectfully with people who think differently
403. Whenever you see the word 'clever', substitute it with 'self-indulgent'.
404. Whenever you see the word 'clever', substitute it with 'self-indulgent'. ~ Don Norman
405. Metaphors & memes are powerful but limit your audience to whoever understands them
406. When someone doesn't understand your code, assume some responsibility
407. Kip Thorne, The Science of Interstellar:
408. “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:
409. Be Courageous
410. Be Courageous Write Boring Code
411. Be Courageous Write Boring Code _
412. The end. Again.
413. The end. Again. The end. Again.
414. My name is Justin Searls
     Please tweet me @searls &
     Say hello@testdouble.com
415. Please say hello if your team could use our team's help E
416. Like everyone, we're hiring!
     Just join@testdouble.com
417. Please find me, whether to chat or to grab a sticker!
418. My name is Justin Searls
     Please tweet me @searls &
     Say hello@testdouble.com