Being An Apprentice Software Crafter

Transcript

1. Being an Apprentice Software CraftER erkan_erol_
2. erkan_erol_ Co-organizer ScTurkey Software Developer SAP DCT
3. DISCLAIMER This presentation contains so much copy/paste content from some conference talks, blog posts and books. References are available in the speaker notes. bit.ly/erkanerol-apprenticeship Opinions are my own and not the views of my employer.
4. Apprenticeship Software Development Craftsmanship
5. SOFTWARE DEVELOPMENT as a profession
7. The Greek physician Hippocrates (460–370 BC) Hippocratic Oath MEDICINE: patient confidentiality
8. Cicero Denounces Catiline, fresco by Cesare Maccari 1882–1888 Code of Hammurabi 1754 BCE LEGAL: presumption of innocence
9. DO WE HAVE SUCH PROFESSION RULES?
10. DO WE HAVE CERTAIN PRACTICES WHICH EVERYBODY ALWAYS FOLLOWS?
11. IS “SOFTWARE DEVELOPMENT” a PROFESSION?
12. Let’s take a closer look
15. universal computing machine • m-configurations • states • a tape • symbols • scanned from a square • printed to a square
16. 1939: THE BOMBE
17. 1942: COLLOSUS
18. 1945: MERCURY DELAY LINES
19. 1945: CRT MEMORY
20. 1945: Automatic Computing Engine
21. 1945: TURING WRITES CODE • In binary. (base 32 reversed) • Uses integer “add” and logical “not” • Invents subroutine • Invents code stack • Invents floating point
22. 1945 “We shall need a great number of mathematicians of ability because there will probably be a good deal of work of this kind to be done.”
23. 1945 “One of our difficulties will be the maintenance of an appropriate discipline, so that we do not lose track of what we are doing”
24. 1945 # of computers in the world: n n ∈ N, 1 < n < 10
25. 1951: Core MEMORY
26. 1950S
27. 1953 FORTRAN
28. 1912-1954
29. 1958: LISP FUNCTIONAL PROGRAMMING
30. 1954 - 1960
31. 1960 # of computers in the world: 100n n ∈ N, 1 < n < 10
32. 1960 # of programmers in the world: 1000n n ∈ N, 1 < n < 10
33. 1950S Programmers were drawn from: • Engineers • Scientists • Mathematicians
34. TRANSISTORS
36. 1965 # of computers in the world: 10,000n n ∈ N, 1 < n < 10
37. 1965 # of programmers in the world: 100,000n n ∈ N, 1 < n < 10
38. 1965 • Not Enough: Engineers, Scientists, Mathematicians • No CS Grads • Programmers drawn from: Best and brightest Accountants, Planners, etc.
39. 1965 Though not mathematicians, they were. They are experienced, disciplined and professionals. Turing would likely have approved.
40. 1966 IBM SELLS 1000 S/360 EVERY MONTH
41. 1966 - SIMULA-67 OLE-JOHAN DAHL KRISTEN NYGARD OBJECT ORIENTATION
42. 1968 - GOTO EDSGER DIJKSTRA - STRUCTURED PROGRAMMING
43. 1968 - C aND UNIX KEN THOMPSON DENNIS RITCHIE
45. 1970 # of computers in the world: 100,000n n ∈ N, 1 < n < 10
46. 1970 # of programmers in the world: 1,000,000n n ∈ N, 1 < n < 10
47. Now Remember • Up to now programmers were disciplined professionals. • They didn’t need a lot of management • They knew how to manage their time, communicate, and work together.
48. MIRACLES! • IBM 360 Virtual Memory OS • NASA: Mercury, Gemini, Apollo • Structured, Functional, Object-Oriented • Fortran, Cobol, Algol, Lisp, C, Unix
49. 1970s Tens of thousands of new CS & EE Grads They were all young and almost all male.
50. 1970- 1995 Number of programmers doubles every five years.
51. 1970- 1995 It means Half of them have less than five years experience!
52. 1970s-1990s foundational theories and practices of software engineering came into being
53. 1970s-1990s The idea was to equate software engineering with physical engineering and borrow as much as possible from the design and building actual.
54. WATERFALL
55. Software Crisis • over-budget • over-time • inefficient • low quality • does not meet requirements • difficult to maintain • never delivered
56. 1975 -> 1982 -> 1995
57. NO SILVER BULLET - 1986
58. 1990s: APPLICATION DELIVERY LAG
59. 1995 Original cohort of disciplined professionals retires. The first wave of career programmers comes of age (well over 40). They foresee the need for change.
63. 2001: Snowbırd
64. AGILE MANIFESTO
65. RAPID ADOPTION
68. CERTIFICATION
71. CRAFTSMANSHIP as an ideology
72. Turing: Discipline and Ability Agile was about Discipline. XP was about Craftsmanship.
73. Agile Business Practices Craftsmanship Technical Practices AGILE SPLIT
74. Irony A goal for Agile: Healing of the divide between business and programming. - Kent Beck
75. “lose track of what we are doing” - Turing
76. AGILE 2008: CRAFTSMANSHIP OVER CRAP
77. DEC 2008
78. MAR 2009
79. AGILE vS CRAFTSMANSHIP building the right thing vs building the thing right
80. MOVEMENT
81. Software Craftsmanship is “an ideology or a mindset”
82. Software Craftsmanship is “a long journey to mastery”
83. Software Craftsmanship is “about professionalism in software development.”
84. Software Craftsmanship is not • Beautiful code • Test-Driven Development • Self-selected group of people • Specific technologies or methodologies • Certifications • Religion
85. UNCLE BOB We must Grow Up Define our profession Choose our practices and disciplines Reunify Agile / Craftsmanship
86. Business doesn’t understand us They cannot evaluate, endorse or approve any technical practices.
87. WE HAVE TO SAVE OUR PROFESSION!
88. APPRENTICESHIP as an attitude
89. APPRENTICES IN THE WILD
90. THEY ARE PASSIONATE!
91. NOT A 9 to 5 professıon
96. You can not do this job with laziness (The story of Fatih Arslan is continuing)
97. THEY ARE LEARNING LIKE CRAZY • Books • Blogs • Videos • Conferences • Meetups
98. WHAT IS THE PROBLEM?
100. THE SCIENCE BEHIND THE BEAN
101. COFFEE LOVERS KNOW COFFEE
102. The second law of thermodynamics: the total entropy of an isolated system can never decrease over time. chemists know “MATTER”
103. THEY KNOW “SOFTWARE” https://www.youtube.com/watch?v=jWj-cMGQMeA
104. THEY KNOW PRINCIPLES • Inversion of Control • Cohesion / Coupling • Separation of Concerns • KISS • SOLID • Law of Demeter • Orthogonality
105. THEY KNOW TECHNIQUES
106. THEY HAVE CONCRETE SKILLS C++ UNIX JAVA HTTP GO JS ECLIPSE VIM k8s VSCODE RAILS SPRING DOCKER GIT REACT
107. THEY DO PRACTICE
108. HOW TO PRACTICE? • CHALLENGE • REPEAT • FEEDBACK
109. HOW TO PRACTICE? NO PRESSURE Do not complete the task, master it!
110. codekata.com
111. NOT ALONE!
114. THEY HAVE SOFT SKILLS
116. SOFTWARE DEVELOPMENT requıres effectıve communıcatıon skılls!
118. THEY ARE HUMBLE!
119. Egoless Programming • You are not your code. • Critique code instead of people – be kind to the coder, not to the code. • Treat people who know less than you with respect, deference, and patience. • Fight for what you believe, but gracefully accept defeat.
120. The Humble Programmer “The competent programmer is fully aware of the strictly limited size of his own skull; therefore he approaches the programming task in full humility, and among other things he avoids clever tricks like the plague.” - Edsger W. Dijkstra
121. THEY OWN THEIR CAREER!
123. THEY BUILD COMMUNITIES
126. INTERACTION SAVES YOU!
127. THEY HAVE PET PROJECTS
128. open source is eating the world opensource.guide
129. THEY ARE HonesT and BRAVE
130. PROFESSIONALISM, PRAGMATISM, PRIDE
131. WRAP UP
132. THANKS FOR LISTENING bit.ly/erkanerol-apprenticeship