Downloaded 92 times
Uploaded byMike Clement
Software Craftsmanship and Agile Code Games
The document discusses software craftsmanship and agile development principles, emphasizing values such as customer satisfaction, adaptability to change, and collaboration between business and developers. It outlines various practices, including coding games and coderetreats, to foster learning and improve software quality. Resources and references for further reading are also provided to encourage community engagement and professional development.
More Related Content
![Chat Application [Full Documentation]](https://cdn.slidesharecdn.com/ss_thumbnails/finaldoconchatapp-170418182505-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
Similar to Software Craftsmanship and Agile Code Games
![UiPath Automation Suite Installation (Hands-On) [2/3]](https://cdn.slidesharecdn.com/ss_thumbnails/automationsuitecommunitysession2-251015095633-a6d862f1-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
Software Craftsmanship and Agile Code Games
- 1. Software Craftsmanship and AgileCode Games Mike Clement @mdclement mike@softwareontheside.com http://blog.softwareontheside.com http://agilecodegames.com
- 2. “Often the truevalue of a thing isn’t the thing itself, but instead is the activity that created it.” -Dave Thomas
- 3. Manifesto for AgileSoftware Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
- 4. Principles of AgileSoftware Development • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. • Welcome changing requirements, even late in development. • Deliver working software frequently. • Business people and developers must work together daily throughout the project. • Build projects around motivated individuals. • The most efficient and effective method of conveying information is face-to-face conversation. • Working software is the primary measure of progress. • Agile processes promote sustainable development. • Continuous attention to technical excellence and good design enhances agility. • Simplicity--the art of maximizing the amount of work not done--is essential. • The best architectures, requirements, and designs emerge from self-organizing teams. • At regular intervals, the team reflects on how to become more effective, then adjusts accordingly.
- 5. Principles of AgileSoftware Development • satisfy the customer • changing requirements • deliver frequently • work together • motivated individuals • face-to-face conversation • working software • sustainable development • technical excellence • simplicity • emerge from self-organizing teams • team reflects
- 6. Principles of AgileSoftware Development • satisfy the customer • changing requirements • deliver frequently • work together • motivated individuals • face-to-face conversation • working software • sustainable development • technical excellence • simplicity • emerge from self-organizing teams • team reflects
- 7. Continuous attention to technicalexcellence and good design enhances agility.
- 8. Literature Roots (1999and 2001)
- 9. Clean Code –August 2008
- 10. Manifesto for SoftwareCraftsmanship As aspiring Software Craftsmen we are raising the bar of professional software development by practicing it and helping others learn the craft. Through this work we have come to value: Not only working software, but also well-crafted software Not only responding to change, but also steadily adding value Not only individuals and interactions, but also a community of professionals Not only customer collaboration, but also productive partnerships That is, in pursuit of the items on the left we have found the items on the right to be indispensable.
- 11. Apprenticeship Patterns –October 2009
- 12. The Clean Coder– May 2011
- 13. Software Craftsmanship –2013/2014
- 14. Quality Code –November 2013
- 15. Software Engineering? Engineering isthe application of scientific, economic, social, and practical knowledge in order to design, build, maintain, and improve structures, machines, devices, systems, materials and processes. • Civil Engineers – do they drive rivets? • Automotive Engineers – do they assemble cars? • Computer Engineers – do they fabricate processors? • Software Engineers – do they write code?
- 16.
- 17. “Going slow todayto go fast tomorrow”
- 18. “Going deliberately todayto not be stuck tomorrow” – Me
- 19. “The only wayto go fast, is to go well” – Uncle Bob
- 20. “Optimize for readtime, not write time” – Me
- 21. Things that SoftwareCraftsmen Value • Growth mindset • Adapting and changing • Share over hoarding • Safety to experiment • Taking control of own destiny • Inclusiveness • Skill-centric over process-centric • Situated Learning
- 22. Things that SoftwareCraftsmen Value • Growth mindset • Adapting and changing • Share over hoarding • Safety to experiment • Taking control of own destiny • Inclusiveness • Skill-centric over process-centric • Situated learning
- 23. Situated learning islearning that takes place in the same context in which it is applied.
- 30. Agile Code Games Howto learn without really trying
- 31. “Often the truevalue of a thing isn’t the thing itself, but instead is the activity that created it.” -Dave Thomas
- 32. Code Katas The scalesand etudes of developing software
- 33. Part of aGuided Kata FizzBuzz
- 34. Solo Randori Coding upa problem, probably repeatedly (sometimes referred to as a kata)
- 35. Problem Description Once upona time there was a series of 5 books about a very English hero called Harry. (At least when this Kata was invented, there were only 5. Since then they have multiplied) Children all over the world thought he was fantastic, and, of course, so did the publisher. So in a gesture of immense generosity to mankind, (and to increase sales) they set up the following pricing model to take advantage of Harry's magical powers. One copy of any of the five books costs 8 EUR. If, however, you buy two different books from the series, you get a 5% discount on those two books. If you buy 3 different books, you get a 10% discount. With 4 different books, you get a 20% discount. If you go the whole hog, and buy all 5, you get a huge 25% discount. Note that if you buy, say, four books, of which 3 are different titles, you get a 10% discount on the 3 that form part of a set, but the fourth book still costs 8 EUR. Potter mania is sweeping the country and parents of teenagers everywhere are queueing up with shopping baskets overflowing with Potter books. Your mission is to write a piece of code to calculate the price of any conceivable shopping basket, giving as big a discount as possible. For example, how much does this basket of books cost? 2 copies of the first book 2 copies of the second book 2 copies of the third book 1 copy of the fourth book 1 copy of the fifth book (answer: 51.20 EUR) http://www.codingdojo.org/cgi-bin/index.pl?action=browse&id=KataPotter&revision=41
- 36. Wasa Coding up aproblem, with a pair
- 37.
- 38. Quick Concepts TDD • Red •Green • Refactor Simple Design • Passes all tests • Clear, expressive, consistent • No duplication • Minimal
- 39. Ways to getGreen • Fake it • Obvious implementation • Triangulation
- 40. Rules • Pair Programming •Use TDD • Everyone should be following • Pair should be explaining • Audience gives suggestions only with when Green • Today: Will switch pairs about every 2 minutes
- 41. Numbers to LCD 123456789 Translatesto: // _ _ _ _ _ _ _ // | _| _||_||_ |_ ||_||_| // ||_ _| | _||_| ||_| _|
- 42. Problem/Kata Lists • http://codingdojo.org/ •http://codekata.com/ • http://katas.softwarecraftsmanship.org/
- 43. Koans The Path toEnlightenment
- 44. Example Koans • Rubyhttp://rubykoans.com/ • F# https://github.com/ChrisMarinos/FSharpKoans • Javascript https://github.com/liammclennan/JavaScript-Koans • Javascript https://github.com/mrdavidlaing/javascript-koans • Intro to programming using Javascript https://github.com/greatersum/intro-to-programming-using- javascript-koans • Linq http://linqkoans.codeplex.com/ • Approval Tests https://github.com/approvals/ApprovalTests.Net.Koans
- 45. Coderetreat A day likeno other
- 46. Structure of Coderetreat •Duration: 8:30am to 5 or 6pm (provide breakfast and lunch, not pizza) • Problem: Conway's Game of Life • Length of Session: 45 minutes (5 or 6 sessions usually) • Pair-programming is necessary, as the knowledge transfer contained in that activity is essential to the practice • Prefer using Test-Driven Development (TDD) • After each session, pairs should be swapped • After each session, code must be deleted, not put in a branch, not stashed, just deleted with no trace left
- 47. Activities/Constraints • Explore theproblem • Ping pong – intro to pairing techniques • No mouse • Paper only
- 48. Activities/Constraints • No nakedprimitives • No conditionals • No loops • Only 2, 3, 4 lines per method • Immutable • Mute • Evil pair/find the loophole • Mute with find the loophole • Tell, don’t ask • TDD as if you meant it
- 49. Experience + Reflection= Learning
- 50. Closing Circle • What,if anything, did you learn today? • What, if anything, surprised you today? • What, if anything, will you do differently in the future?
- 51. Mob Programming Like Randori,but larger switching cycles, and a real team working on a real system throughout the day
- 53. One navigator, manypairs
- 55.
- 57. Greater Sum Workshops •2 hours • Opening Circle • Name • Programming Experience • Silly question (What’s your favorite… ?) • Mobbing! • Possibly “One navigator, many mobs” • Closing Circle • Borrowed from Coderetreat
- 58. Software Craftsmanship Atlantaand Utah Software Craftsmanship Format Our meeting format differs from your usual technology user group. At a meeting we have: • 0-3 Lightning talks (up to but not over 5 minutes each) • ~30 min - Reading Discussion • ~60 min - Interactive Craftsman-run Coding Exercise (based on the principles of a Coding Dojo)
- 59. “Often the truevalue of a thing isn’t the thing itself, but instead is the activity that created it.” -Dave Thomas
- 60. Books • The PragmaticProgrammer: From Journeyman to Master • Clean Code • Apprenticeship Patterns (free online) • The Clean Coder • Software Craftsmanship: Professionalism, Pragmatism, Pride • Quality Code: Software Testing Principles, Practices, and Patterns • The Coding Dojo Handbook
- 61. Resources • http://agilemanifesto.org/ • http://manifesto.softwarecraftsmanship.org/ •http://coderetreat.org/ • http://mobprogramming.org/ • http://www.agilecodegames.com/
- 62. Mike Clement • @mdclement •mike@softwareontheside.com • http://blog.softwareontheside.com • http://agilecodegames.com • https://github.com/mdclement • http://www.greatersum.com • Software Craftsmanship Atlanta – first Wed at 6pm
Editor's Notes
- #3 Verbs vs. Nouns Requirements “Plans are useless, but planning is invaluable” – Dwight D. Eisenhower the value is the process that everyone goes through in order to produce the document: the understanding gained, the relationships forged, the negotiations, the compromises, and all the other little interactions which share information. Quality Plan, measure, build a quality product! Quality is PART OF THE PROCESS. Quality is in the spirit of the smallest of our daily activities.
- #10 A Handbook for Agile Software Craftsmanship
- #11 March 2009 A manifesto to complement the Agile Manifesto
- #15 Mostly about software testing, but great intro that talks about why code quality is important and uses the context of craftsmanship
- #16 Do any other professionals that use the title “engineer” work all the way through the process, from design to building to testing? So, while there are aspects of engineering in software, there is just as much craft.
- #17 Notes from recent discussion at the Salt Lake Agile Roundtable – question was “What’s different about Software Craftsmen? Why should a company care?”
- #29 Great for what it says, trying F#, but if you really want to learn how to use it, you need to use it in the environment in which you will use it for real.
- #31 Agile community has “Agile Games” that facilitate learning of agile/lean principles Emily Bache talks about many of these as part of a catalog of activities that you would do at a Coding Dojo, but I wanted to broaden the scope.
- #32 Verbs vs. Nouns Requirements “Plans are useless, but planning is invaluable” – Dwight D. Eisenhower the value is the process that everyone goes through in order to produce the document: the understanding gained, the relationships forged, the negotiations, the compromises, and all the other little interactions which share information. Quality Plan, measure, build a quality product! Quality is PART OF THE PROCESS. Quality is in the spirit of the smallest of our daily activities.
- #33 Japanese word describing detailed choreographed patterns of movements practiced either solo or in pairs. A kata is a coding exercise that performed repeatedly and perfected. Practicing a specific skill
- #39 Familiarity with TDD Familiarity with Principles of Simple Design
- #41 if anyone is lost, pair should explain – audience can ask clarifying questions, but not give suggestions unless Green
- #44 A story, dialog, question or statement which is used to test a students progress.
- #51 From a practical standpoint, if you facilitate a coderetreat, it’s best to give the group some time to reflect (3-5 minutes) and then write down their own answers to these questions so that the circle can move quickly.
- #59 Currently reading Apprenticeship Patterns
- #60 Verbs vs. Nouns Requirements “Plans are useless, but planning is invaluable” – Dwight D. Eisenhower the value is the process that everyone goes through in order to produce the document: the understanding gained, the relationships forged, the negotiations, the compromises, and all the other little interactions which share information. Quality Plan, measure, build a quality product! Quality is PART OF THE PROCESS. Quality is in the spirit of the smallest of our daily activities.