The document discusses reducing passive interruptions when coding. It notes that programmers can take 10-15 minutes to resume work after an interruption and lose their context and flow. Passive interruptions occur when waiting for feedback like test results or page loads. The document advocates for reducing these interruptions through techniques like instant code reloading, fast tests, and immediate feedback to allow programmers to stay in flow. It argues this is important for designing and verifying ideas quickly during development.
3. Modern software development includes automated testing
strategies and automated deployment pipelines that take the
friction out of the deployment process
Mary Poppendieck
http://www.leanessays.com/2015/08/friction.html
16. A programmer takes between 10-15 minutes to start
editing code after resuming work from an interruption
Programmer Interrupted
by Chris Parnin
2013-01-19
Unacceptable!
17. Every time you are interrupted
you lose the context
Context
18. Flow
(…) is the mental state of operation in
which a person performing an activity is
fully immersed in a feeling of energized
focus, full involvement, and enjoyment
in the process of the activity.
"Scout Girl in Concentration"
by Randy
27. Passive Interruption
Period of time in which we are interrupted, waiting for a
feedback in order to resume our flow of thinking
28. The passive interruption has
similar effect of the interruption
caused by a person
Hypothesis
I’m not being interrupted because I can think about
the next steps while I’m waiting
29. I’m not being interrupted because I can think about
the next steps while I’m waiting
Are you sure
VerifyCode Verify CodeVerifyCode Code
30. I’m not being interrupted because I can think about
the next steps while I’m waiting
Are you sure
VerifyVerifyCode CodeVerify Code
31. Well, you can write a lot of code and after that you
can test it all together
The passive interruption has
similar effect of the interruption
caused by a person
Hypothesis
32. Well, you can write a lot of code and after that you
can test it all together
Are you sure
VerifyCode Verify CodeVerifyCode Code
33. Well, you can write a lot of code and after that you
can test it all together
Are you sure
VerifyCode
34.
35.
36.
37. Much of agile thinking is about setting up feedback loops so that
we can learn more quickly
Martin Fowler
38. It isn’t because you can write a lot of code and after
that you can test it
Are you sure
VerifyCode
39. It isn’t because you can write a lot of code and after
that you can test it
Are you sure
VerifyCode VerifyCode VerifyCode VerifyCode
baby steps!
84. If it (test) takes ten seconds just to start testing, toss it!
Allow nothing to slow down your tests.
Test Time
03 September 2014
by Robert C. Martin (Uncle Bob)