Slide 1
Slide 1 text
In Praise of Smallness
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
No content
Slide 6
Slide 6 text
3:00
Slide 7
Slide 7 text
9:00
Slide 8
Slide 8 text
No content
Slide 9
Slide 9 text
CAPITAL
EXPENDITURE
END TO END
CAPACITY
PLANNING
ENTERPRISE
GOVERNANCE
OPERATIONAL
RUN BOOK
DATABASE
SHARDING
DISASTER
RECOVERY
PCI COMPLIANCE
Slide 10
Slide 10 text
http://www.flickr.com/photos/90425101@N00/8722350677
Slide 11
Slide 11 text
3:00
Slide 12
Slide 12 text
B.J. Allen
Slide 13
Slide 13 text
No content
Slide 14
Slide 14 text
https://cml.music.utexas.edu
Robert Duke
Director, Center for Music Learning
Butler School of Music
The University of Texas at Austin
Slide 15
Slide 15 text
No content
Slide 16
Slide 16 text
No content
Slide 17
Slide 17 text
No content
Slide 18
Slide 18 text
“students ... were randomly assigned to be quizzed at one
of two frequencies – monthly or semimonthly. The group
quizzed twice a month outperformed the less frequently
quizzed group […] on both an end-of-semester
examination and a delayed recall test administered 3
months later”
(Kalaf & Hanna, 1992)
“we examined whether low-stakes testing (quizzing) can
be used to foster students’ learning ...Quizzing produced
significant learning benefits, with between 13% and 25%
gains in performance on summative unit examinations.”
(Pennebaker, Gosling & Ferell, 2013)
Slide 19
Slide 19 text
No content
Slide 20
Slide 20 text
No content
Slide 21
Slide 21 text
No content
Slide 22
Slide 22 text
Approval Mistakes
Slide 23
Slide 23 text
No content
Slide 24
Slide 24 text
No content
Slide 25
Slide 25 text
Negative
!
!=
!
Negative
Slide 26
Slide 26 text
Negative Feedback Must Be:
• Accurate
• Contextually appropriate
• Delivered without emotion
Slide 27
Slide 27 text
No content
Slide 28
Slide 28 text
3.0.21???
Slide 29
Slide 29 text
→
3.0 3.1
Slide 30
Slide 30 text
→
3.1 3.2
Slide 31
Slide 31 text
No content
Slide 32
Slide 32 text
No content
Slide 33
Slide 33 text
No content
Slide 34
Slide 34 text
No content
Slide 35
Slide 35 text
No content
Slide 36
Slide 36 text
http://www.informit.com/articles/article.aspx?p=1833567
When a release engineering team spends a
weekend in a data center deploying the last
three months' work, the last thing anybody
wants to do is deploy again any time soon.
– Jez Humble
Slide 37
Slide 37 text
No content
Slide 38
Slide 38 text
Upgrading all […] components in one big-bang release
is the highest-risk way to roll out new functionality.
Instead, deploy components independently.
!
Database changes can also be rolled out incrementally.
Principle 1: Low-Risk Releases Are Incremental
Slide 39
Slide 39 text
No content
Slide 40
Slide 40 text
Deployment is what happens when you install some
version of your software into a particular environment.
!
Release is when you make a system or some part of it
(for example, a feature) available to users.
Principle 2: Decouple Deployment and Release
Slide 41
Slide 41 text
No content
Slide 42
Slide 42 text
No content
Slide 43
Slide 43 text
When you deploy to production more often, you're
practicing the deployment process more often.
!
When you're deploying more frequently, working out
what went wrong is much easier because the amount
of change is much smaller.
Principle 3: Focus on Reducing Batch Size
Slide 44
Slide 44 text
Story is almost done
rush it wait forever*
*not really forever
Slide 45
Slide 45 text
Story is almost done
wait a short time*
*really a short time
rush it
Slide 46
Slide 46 text
No content
Slide 47
Slide 47 text
No content
Slide 48
Slide 48 text
Thank You!
Slide 49
Slide 49 text
@bjallen