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.

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

Working with Git in Terminal (Prep)

• Initialise a Git repository from the terminal

Adding & Committing (Prep)

• Stage a change using the terminal
• Make a commit using the terminal
• Check the status of a repository
• Access the commit history

Remote Repositories (Prep)

• Link local and remote repositories using the terminal

Pushing & Pulling (Prep)

• Push to a remote repository from the terminal
• Configure a default upstream

Branching & Merging (Prep)

• Create a branch in a repository from the terminal
• Merge two branches in the terminal
• Delete a branch

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.

Developer Tools (Day Plan)

• Inspect the DOM
• Identify the values of design tokens in the CSS
• Alter the values of the CSS Variables using DevTools
• Select the Grid Badge in the Elements panel
• Use the Grid Editor to change layout
• Run a Lighthouse audit
• Identify and resolve the reported issues
• Find the MDN docs links in the Styles panel
• Find a different API using the same code
• Inspect the Accessibility Tree and compare it to the DOM

Clean Code (Day Plan)

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