This document summarizes the third meeting of a Software Craftsmanship group. The agenda included discussions of clean code principles like SOLID and DRY. There was also a hands-on coding dojo to practice techniques like test-driven development and refactoring. The group believes in principles from the Software Craftsmanship Manifesto like short iterations, readable code, and automated testing. The meeting included both lectures and a coding dojo hands-on session to identify suspected Lychrel numbers through iterative calculations.
Convert to study guideBETA
Transform any presentation into a summarized study guide, highlighting the most important points and key insights.
5. Software CraftsmanshipSoftware Craftsmanship Manifestohttp://manifesto.softwarecraftsmanship.org/Manifesto:>comprehensive documentation> following a plan> processes & tools> contract negotiationThat is, in pursuit of the items on the left we have found the items on the right to be indispensable
6. Software CraftsmanshipHow?Short IterationsReadable Code (OOP Best Practices)Test Driven Development (TDD), Unit Testing & Acceptance TestsIterative Design (SOLID & OOD Best Practices)RefactoringAutomatic Builds / Continuous IntegrationAutomate Every Possible ProcessIDE & ToolsCode Reviews / Pair Programming Apprenticing Exercising Deliberate PracticeLearning TechniquesCode KatasProductive PartnershipWell-craftedSteadily adding valueCommunity of Professionals
11. IsLychrel()Lychrel Number Anatural numberwhich cannotform palindromethrough theiterativeprocess of repeatedly reversing itsbase 10digits and adding the resulting numbers56 isnt Lychrel after one iteration: 56+65 =12157 isnt Lychrelafter two iterations: 57+75 = 132, 132+231 =363.59 is not a Lychrelafter 3 iterations: 59+95 = 154, 154+451 = 605, 605+506 =1111