Compiled Learning Objectives

12 vs 24 hour clock

• Identify a pattern between a set of inputs and outputs produced by a given function

Comparing current and target output

• Evaluate an expression that uses a comparison operator
• Explain when to use the === operator in a program
• List the values of the boolean type

Writing an assertion

• Describe the difference between console.log and console.assert
• Write an assertion to check for some behaviour of a given function
• Implement a piece of functionality specified in an assertion
• Given an assertion and a function declaration, identify and explain whether the assertion will succeed or fail
• Write an assertion for a function that implements a solution to a given problem

Interpreting errors

• Interpret an error trace to identify which line in which file caused the error
• Identify an error message from an error trace

Interpreting this error

• Interpret an error message
• Break down an error message and look up unfamiliar parts
• Rephrase an error message

Reusing variable names

• Fix code which declares the same identifier more than once

Making a choice

• Propose a strategy for solving a problem
• Identify sub-problems within a larger problem

Conditionally executing code

• Construct a flow diagram that describes how to produce an output from a given input
• Explain when it is necessary to use a conditional statement
• Identify the syntactic features of an if statement
• Analyse a conditional statement to determine whether or not the statement will be executed
• Determine the output of a program that uses a conditional statement

Forming sub-goals

• Define a sub-goal
• Explain why we use sub-goals

Accessing strings

• Define zero-indexing
• Given a short program, determine the return value of a call to slice on a string before execution
• Describe how to convert a string into a number in JavaScript

Testing a sub-goal

• Test a solution to a sub-goal before solving the whole problem

Sub-goal #2

• Explain how different concepts are combined to solve a goal

Refactoring repetition

• Refactor code to remove duplication
• Explain why duplicated code can cause problems

Identifying missing tests

• Define groups of input
• Define edge cases
• Identify groups of input for a function
• Identify edge cases for a function

03 Play the CLI Treasure Hunt

• traverse a filesystem using Unix commands

06 🫱🏽‍🫲🏿 Mentored pair programming

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

Stand Up

• Explain the format of a stand-up meeting
• Identify the purpose of a stand-up meeting
• Share a progress update in a stand-up meeting

Study Group Development

• Create a strategy for implementing a program based on a set of requirements.
• Express questions, problems and blockers as formal bug reports
• Interpret business requirements and express them as test cases.
• Open a pull request and iterate on it in response to feedback.