• TC1 Logic: writes good quality code (logic) with sound syntax in at least one language
• TC4 Test: can test code and analyse results to correct errors found using either V-model manual testing and/or using unit testing
• TC10 Can apply good practice approaches according to the relevant paradigm (for example object oriented, event driven or procedural)

• Slides
• Laptops
• Internet access
• Post-its
• Markers
• A3 paper for apprentices to draw on
• Whiteboard (or flipcharts if this is not possible)

One mentor required per three apprentices (leads can act as mentors). These should be able to cover support for the required languages.

Several exercises (katas and code starters) will need to be ported to required languages if not already done.

• Make sure you can sign in to miro.com with your own account
• Make sure you can sign in to github.com with you own account
• If you use Java, have least JDK 8 or later and a working IDE
• If you use JavaScript, have Node.js v14.15.0 or later installed
• If you use C#, have Visual Studio installed

Organisation mentors should look to exercise the knowledge we’ve covered in the boot camp. Below are suggestions for tasks that would do this, but please use your own judgement to work out what to do. There is no need for anything to be returned to MD or the presenters—it’s just a learning exercise.

• Draw a diagram showing how the classes interact in some code you have been working on
• They should identify Encapsulation, Abstraction, Inheritance, Polymorphism (this might require some discussion)
• Take a look at one of your codebases and find examples of classes with multiple responsibilities
• Try to improve some existing classes or methods with multiple responsibilities by using some of the OO principals
• Finish off the exercises started at the boot camp (checkout kata for example)

• Supermarket Kata
• The Secret behind the Single Responsibility Principle on Hacker Noon
• Clean Code by Robert C Martin
• Duplicate Code ‘Code Smell’

The slides can be viewed from the link at the top of the repository.

• Identify objects from business scenario (groups)
• Model a pack of playing cards (groups)
• Use abstraction to make the Snap! game work for normal cards (groups)
• Refactor the card model using inheritance (groups)
• Use polymorphism to implement Super Snap! using a mixture of card types
• Adapting Checkout Kata (pairs)
• Separating responsibilities from Checkout Kata (pairs)

• Programming paradigms
• Why OO?
• How to think about objects

• Why source control
• Create, clone, commit, push

• Modelling some classic scenarios with objects
• Principles
  • Encapsulation
    • Apply to modelling
    • Rewrite some existing code to remove inappropriate intimacy and coupling
    • Code review some existing code
  • Abstraction
    • Apply to modelling
    • Rewrite some existing code to abstract complexity
    • Explain difference between encapsulation and abstraction
    • Introduce to interfaces
  • Polymorphism
    • Apply to modelling
    • Give some examples
  • Inheritance

• Cohesion
• Functional Decomposition
• Critiquing and adapting poorly implemented checkout kata