One hour presentation given at KGISL Institute of Technology, Coimbatore, India.

1. Software
Professionalism
KGISL, Coimbatore, July 2015
@JonJagger
jon@jaggersoft.com

2. how to perform
deliberate practice
KGISL, Coimbatore, July 2015
@JonJagger
jon@jaggersoft.com

3. 3

4. 4

5. 5

6. 6

7. 7

8. 8

9. 9

10. 10

11. 11

12. 12

13. 13

14. 14

15. 15
cyber-dojo.org
server

16. 16
cyber-dojo.org
server
git
commit

17. 17
cyber-dojo.org
server

18. 18
cyber-dojo.org
server

19. 19

20. 20
one or more
tests failed

21. 21
all tests
passed

22. 22
syntax
error

23. 23

24. 24

25. 25

26. 26

27. 27
review dashboard

28. 28
oldest newest summaries

29. 29
1 minute

30. 30

31. 31
diff

32. 32

33. Deliberate Practice
doing something you can't
comfortably do (yet)
effort
awareness

34. Incidental Practice
effort
awareness
doing something you can
already comfortably do

35. effort
awareness
effort
awareness

36. The total absence of
meaningful practice...
is probably the
dominant factor that
keeps... teams from
being effective
learning units.

37. Deliberate practice
is designed, so it
can be designed
well or badly.

38. Principle of
Company

39. Francis Bacon 1561-1626
Man prefers to
believe that
which he prefers
to be true.

40. We are all
lousy self
evaluators.

41. ?% of high school
seniors believe
their leadership
skills are below
average.

42. 2% of high school
seniors believe
their leadership
skills are below
average.

43. company

44. pairing

45. team

46. Principle of
Provocation

47. We must first put our
students into a
provocative environment.
...
If there is no provocation,
there is no learning.

48. minimal!
•no code completion
•no refactoring support
•no colour syntax
•no compile button
•no save button
•no ...

49. pairing!

50. nowhere to hide!
diff
diff
diff

51. company & anonymity

52. Principle
of Repetition

53. Who is this?

54. Who are they?

55. There is
absolutely no
evidence of a
fast track for
high achievers.

56. Mozart ... worked till
his hands were deformed.

57. As teenagers, the Beatles worked in
Hamburg, ... doing 8 hour sets, 7 days a
week, for months on end.

58. Principle of
Feedback

59. 59
Scrum Teams deliver
products iteratively and
incrementally, maximizing
opportunities for feedback.
Sprint Review: ... the
presentation of the Increment
is intended to elicit feedback
and foster collaboration.
http://www.scrumguides.org/docs/scrumguide/v1/scrum-guide-us.pdf

60. 60
Feedback
Communication
Simplicity
Courage

61. 61
There is not one living
creature that lacks that
integrated, total
unification through
feedback.
John Gall
How to use conscious purpose
without wrecking everything
http://www.gilb.com/dl539

62. 62
Compared to a frog or
a salamander, our
biggest manmade
systems seem like
simple wind-up toys.
John Gall
How to use conscious purpose
without wrecking everything
http://www.gilb.com/dl539

63. The amount of feedback
built into living
organisms differs by
many orders of
magnitude from the
amount we build into
man-made systems.
John Gall
How to use conscious purpose
without wrecking everything
http://www.gilb.com/dl539

64. 64

65. 65
senses
pancreas
senses
liver &
muscles
causes
glycogen
causes
Hyperglycemia
pancreas
senses
glucagoncauses
senses
causes
insulin
causes
Hypoglycemia
causes

66. 66
Henri Louis Le Chatelier
Systems tend
to oppose
their own
proper
function.

67. 67
All change can be
understood as the
effort to maintain
some constancy,
and all constancy
as maintained
through change.

68. 68
at least two iterations
1st 10.72 19.332nd
average average

69. Principle of
Success
not Failure

70. What number
am I
thinking of?

71. I have not failed.
I've just found
1000 ways that
won't work.
Thomas Edison

72. Learning from failure
only has meaning
when we know what
we mean by success.
Kevlin Henney

73. what do you see?

74. lots of ambers

75. colour-to-colour percentages
7.0%
7.8%
8.0%
8.1%
8.4%
11.1%
11.2%
11.3%
27.1%
lots of
amber
to
amber
random sample of 500 cyber-dojos

76. lots of amber sequences

77. for each colour-to-colour transition
average lines of code added+deleted
3.94
5.39
4.67
4.65
7.52
6.01
17.67
13.65
bigger delta
==
greater chance of
amber
random sample of 500 cyber-dojos

78. long recovery time

79. debugging
waterfall
"test"

80. it’s like making
toast by burning
bread and then
scraping the burn
off!

81. short recovery time
coding
testing

82. specifying
test test test test test
agile

83. •Repetition
•Company
•Provocation
•Feedback
•Success not Failure

84. @JonJagger
jon@jaggersoft.com
thank you for
listening