Compiled Learning Objectives

At the end of the sprint, you should be able to do the following things. Make sure to check you can do them all, and if not, go back and keep practicing until you can.

Ordinal numbers (Prep)

• Convert positions to ordinal numbers

Testing frameworks (Prep)

• Explain why we need to use testing frameworks

Starting a project (Prep)

• Identify a package.json
• Explain the purpose of a package.json

Using packages (Prep)

• Define a dependency
• Define a package
• Identify some benefits of using a third-party party software library when programming
• Describe why need to use npm when we are building JavaScript applications

Installing Jest (Prep)

• Outline the effects of running an installation command, e.g. npm install
• Install a dependency with npm

Jest's Application Programming Interface (Prep)

• Explain why we use APIs in programming
• Identify some commonly used APIs

First test case (Prep)

• Outline the effect of running npm test
• Interpret documentation to determine how part of a third-party API behaves
• Describe what toEqual checks in the Jest library
• State the current return value of a function and the target output for a given test
• Implement a test case to describe the behaviour of a function

Interpreting feedback (Prep)

• Identify current output and target output in test feedback
• Determine the line an error occurred from some test feedback
• Give an example of why Jest makes tests easier to write than console.assert

Dead Code (Prep)

• Define what is meant by ‘dead code’
• Understand why ‘dead code’ matters in the context of working as a software engineer
• Demonstrate how we handle ‘dead code’ in our codebases
• Identify ‘dead code’ in an existing code base

Generalising further (Prep)

• Extend an implementation based on more assertions

Anonymous functions (Prep)

• Explain the difference between a named function and an anonymous function

Arrow functions (Prep)

• Write an arrow function

Testing Workshop (Prep)

• Practice solving problems while testing

Learn from rejections (Backlog)

• Reflect on previous experiences
• Identify key learning points from that experience

Mandatory Sprint 3 Codewars Katas (Backlog)

• Practice applying concepts related to the sprint’s prep material in a kata.
• Problem solve a new coding challenge.

Play the Bandit (Backlog)

• Develop your command line skills

Refactoring Dead Code (Backlog)

• Identify ‘dead code’ in an existing code base
• Demonstrate how we handle ‘dead code’ in our codebases

Stretch Codewars Katas (Backlog)

• Practice applying concepts related to the sprint’s prep material in a kata.
• Problem solve a new coding challenge.

Watch the VSCode Debugger Video (Backlog)

• Learn about the debugging tools built into VSCode

Mentored pair programming (Backlog)

• Talk aloud when thinking about a problem.
• Write code in front of someone else.
• Analyse your strategies for solving problems in code.

warning: name is empty (Day Plan)

• Play computer with a few short programs to work out what happens when they run
• Keep track of your place in a running program using frames
• Describe what happens when a function is called during runtime
• Check your understanding using an application like the Python visualiser

warning: name is empty (Day Plan)

• Identify properties which make code easier to read and modify.
• Compare the cleanliness of code.