The Elements of Style
0 likes187 views
Second version of my talk on XP, code review and pair programming with examples from my early work history. Delivered at Sunderland University 2020 to CS undergraduates.
Convert to study materialsBETA
Transform any presentation into ready-made study materialselect from outputs like summaries, definitions, and practice questions.
The Elements of Style
- 2. hey hi hello derek graham @deejaygraham
- 7. Code?
- 8. Code Review?
- 9. Pairing?
- 10. I invented that
- 25. Code Review
- 27. Pairing
- 30. 4 Hard Problems Cache Invalidation Naming things Off-by-one errors
- 31. Programming is
- 33. Hardest Problem Cache Invalidation Naming things Off-by-one errors Communication
- 34. Why do we write code? To communicate with a machine To communicate with our customers To communicate with ourselves To communicate with our team To communicate with the future
- 35. Always wanted to travel back in time to 鍖ght a younger version of yourself? Software development is the career for you! @Loh
- 36. Edsger Dijkstra "If you want more effective programmers, you will discover that they should not waste their time debugging, they should not introduce the bugs tostartwith."
- 37. Style ?
- 38. Collaborative Styles Individual Swarming Pairing Strong Pairing Mob Programming
- 42. 10 Write Code 20 Ask for Review 30 If Review Goto 40 30 Goto 20 40 Receive Feedback 50 Goto 10
- 43. Pair<dev, dev>
- 45. Navigator Driver
- 46. Driver
- 47. Navigator
- 48. I have an idea, giveme the keyboard
- 49. Swarming
- 51. C# JSON Test Script DB Admin HTML Deploy Script
- 52. Our Team Swarming is the 鍖rst time weve felt like a genuine team instead of individuals all working for the same manager.
- 53. Mob Programming
- 55. Woody Zuill All the brilliant people, working on the same thing, at the same time, in the same space, and at the same computer.
- 57. !Mob
- 60. *reconstruction
- 62. I have an idea, give me the keyboard
- 63. I have an idea, pleasetake the keyboard
- 65. If you have the keyboard, you cant have the ideas
- 66. Why ? Pairing
- 67. Do you ever have bugs?
- 69. Do you ever have typographic anomalies?
- 74. Try Mobbing
- 79. If your code is valuable enough for someone to use, it's valuable enough for them to be upset when it stops working.