JS1 Sprint 3 Day-Plan

Every session begins with an energiser. Usually there’s a rota showing who will lead the energiser. We have some favourite games you can play if you are stuck.

Traffic Jam: re-order the cars to unblock yourself
Telephone: draw the words and write the pictures
Popcorn show and tell: popcorn around the room and show one nearby object or something in your pocket or bag and explain what it means to you.

Learning Objectives

Describe on personal weaknesses
Describe what growth mindset is
Support professional growth of peers

Preparation

n/a

Introduction

The importance of a growth mindset is the ability to be resilient, continuously learning, and the belief that intelligence and abilities can be developed through dedication and effort.

Fixed vs growth mindset

🎯 Goal: To discuss the characteristics of fixed and growth mindsets (20 minutes)

Form small groups (3-4 people) and discuss the characteristics of fixed and growth mindsets.
Write down examples of fixed and growth mindset.
As a class, create a collaborative board (e.g. Google Jamboard).
Share the examples you discussed in your group.
Compare the differences between the two mindsets on the board.

Reflecting on fixed mindset experiences

🎯 Goal: To reflect on one’s instances of a fixed mindset and identify where the growth mindset could have been adopted (20 minutes)

You have written about your fixed mindset experiences as part of the preparation for this session.

Volunteer to share your experience with the class, talk about your past experiences and provide support to each other.

Quiz results discussion

🎯 Goal: To identify the characteristics of growth mindset (15 minutes)

Group people according to their quiz results
- Strong growth mindset.
- Growth mindset but with some fixed ideas
- Fixed mindset, but with some growth ideas
- Strong fixed mindset.
Talk in these groups about how you can support each other. Sharing a common mindset empowers us to support each other in changing.

A quick break of fifteen minutes so we can all concentrate on the next piece of work.

Learning objectives

Formulate acceptance criteria from a problem statement
Create assertions to check different test cases
Implement functionality using assertions
Interpret documentation on JavaScript logical operators

🧰 Setup

In this workshop, you'll need to:

Split up into groups of 4

Context

To begin, you'll need some context.

Use this page 👉 https://www.mathsisfun.com/triangle.html to get the names of different triangles depending on their three side lengths.
There should be 3 different names. Check with each other that you all understand what these names mean.

Problem statement

In this workshop, you'll need to implement a function that takes the three side lengths of a triangle and returns a string indicating whether it is "equilateral", "isoceles" or "scalene"

Acceptance criteria

First, name the function according to the problem statement. The name should be semantic. It should convey what the function does.
Then set out acceptance criteria for your function in the format shown below:

Given …
When …
Then …

🧪 Write your first assertion

Write your first assertion using console.assert to check the functionality. You can write your code in triangles.js

🧱 Start building up your functionality

Once you've got your first assertion down, you'll need to start building out your functionality for this case.

Every Saturday we cook and eat together. We share our food and our stories. We learn about each other and the world. We build community.

This is everyone’s responsibility, so help with what is needed to make this happen, for example, organising the food, setting up the table, washing up, tidying up, etc. You can do something different every week. You don’t need to be constantly responsible for the same task.

What are we doing now?

You’re going to use this time to work through coursework. Your cohort will collectively self-organise to work through the coursework together in your own way. Sort yourselves into groups that work for you.

Use this time wisely

You will have study time in almost every class day. Don’t waste it. Use it to:

work through the coursework
ask questions and get unblocked
give and receive code review
work on your portfolio
develop your own projects

🛎️ Code waiting for review 🔗

Below are trainee coursework Pull Requests that need to be reviewed by volunteers.

Add recommended VS Code extensions 🔗

What does this change?

This PR introduces a curated list of recommended Visual Studio Code extensions to the module. The aim is to standardize the development environment for all trainees, ensuring they have access to essential tools and features that enhance their learning experience, and save our mentors’ time and energy.

Common Content?

This change does not directly modify the common content shared across modules but provides an essential resource that complements the existing curriculum. It ensures that all trainees, regardless of their module, have a consistent set of tools at their disposal.

Block/s

Common Theme?

Yes

Issue number: #368

Org Content?

Module

Checklist

I have read the contributing guidelines
I have checked my spelling and grammar with an automated tool
I have previewed my changes to check the markdown renders as I intend
I have run my code to check it works
My changes follow our Style Guide

Who needs to know about this?

@CodeYourFuture/itp-syllabus-team

Start a review

NW-6 | Fikret Ellek | JS1| [TECH ED] Complete week 4 exercises | WEEK-4 🔗

Learners, PR Template

Self checklist

I have committed my files one by one, on purpose, and for a reason
I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
I have tested my changes
My changes follow the style guide
My changes meet the requirements of this task

Changelist

Briefly explain your PR.

Questions

Ask any questions you have for your reviewer.

Start a review

NW-6 | Fikret Ellek | JS1| [TECH ED] Complete week 3 exercises | WEEK-3 🔗

Learners, PR Template

Self checklist

I have committed my files one by one, on purpose, and for a reason
I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
I have tested my changes
My changes follow the style guide
My changes meet the requirements of this task

Changelist

Briefly explain your PR.

Questions

Ask any questions you have for your reviewer.

Start a review

London_10/Anu Thapaliya/Module-JS1/week2 🔗

Learners, PR Template

Self checklist

I have committed my files one by one, on purpose, and for a reason
I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
I have tested my changes
My changes follow the style guide
My changes meet the requirements of this task

Changelist

Briefly explain your PR.

Questions

Ask any questions you have for your reviewer.

Start a review

NW6 | Pedram Amani | Module-JS1 | Week4 🔗

Learners, PR Template

Self checklist

[ ✓ ] I have committed my files one by one, on purpose, and for a reason
[ ✓ ] I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
[ ✓ ] I have tested my changes
[ ✓ ] My changes follow the style guide
[ ✓ ] My changes meet the requirements of this task

Changelist

Briefly explain your PR.

JavaScript 1 - Week 4 exercises

Questions

Ask any questions you have for your reviewer.

Start a review

See more pull requests

Please feel comfortable and welcome to pray at this time if this is part of your religion.

If you are breastfeeding and would like a private space, please let us know.

What are we doing now?

You’re going to use this time to work through coursework. Your cohort will collectively self-organise to work through the coursework together in your own way. Sort yourselves into groups that work for you.

Use this time wisely

You will have study time in almost every class day. Don’t waste it. Use it to:

work through the coursework
ask questions and get unblocked
give and receive code review
work on your portfolio
develop your own projects

🛎️ Code waiting for review 🔗

Below are trainee coursework Pull Requests that need to be reviewed by volunteers.

Add recommended VS Code extensions 🔗

What does this change?

This PR introduces a curated list of recommended Visual Studio Code extensions to the module. The aim is to standardize the development environment for all trainees, ensuring they have access to essential tools and features that enhance their learning experience, and save our mentors’ time and energy.

Common Content?

This change does not directly modify the common content shared across modules but provides an essential resource that complements the existing curriculum. It ensures that all trainees, regardless of their module, have a consistent set of tools at their disposal.

Block/s

Common Theme?

Yes

Issue number: #368

Org Content?

Module

Checklist

I have read the contributing guidelines
I have checked my spelling and grammar with an automated tool
I have previewed my changes to check the markdown renders as I intend
I have run my code to check it works
My changes follow our Style Guide

Who needs to know about this?

@CodeYourFuture/itp-syllabus-team

Start a review

NW-6 | Fikret Ellek | JS1| [TECH ED] Complete week 4 exercises | WEEK-4 🔗

Learners, PR Template

Self checklist

I have committed my files one by one, on purpose, and for a reason
I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
I have tested my changes
My changes follow the style guide
My changes meet the requirements of this task

Changelist

Briefly explain your PR.

Questions

Ask any questions you have for your reviewer.

Start a review

NW-6 | Fikret Ellek | JS1| [TECH ED] Complete week 3 exercises | WEEK-3 🔗

Learners, PR Template

Self checklist

I have committed my files one by one, on purpose, and for a reason
I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
I have tested my changes
My changes follow the style guide
My changes meet the requirements of this task

Changelist

Briefly explain your PR.

Questions

Ask any questions you have for your reviewer.

Start a review

London_10/Anu Thapaliya/Module-JS1/week2 🔗

Learners, PR Template

Self checklist

I have committed my files one by one, on purpose, and for a reason
I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
I have tested my changes
My changes follow the style guide
My changes meet the requirements of this task

Changelist

Briefly explain your PR.

Questions

Ask any questions you have for your reviewer.

Start a review

NW6 | Pedram Amani | Module-JS1 | Week4 🔗

Learners, PR Template

Self checklist

[ ✓ ] I have committed my files one by one, on purpose, and for a reason
[ ✓ ] I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
[ ✓ ] I have tested my changes
[ ✓ ] My changes follow the style guide
[ ✓ ] My changes meet the requirements of this task

Changelist

Briefly explain your PR.

JavaScript 1 - Week 4 exercises

Questions

Ask any questions you have for your reviewer.

Start a review

See more pull requests

Retro (20 minutes)

A retro is a chance to reflect on this past sprint. You can do this on a Jamboard (make sure someone clicks “Make a copy” before you start, and you work on that together) or on sticky notes on a wall.

Set a timer for 5 minutes.
Write down as many things as you can think of that you’d like to start, stop, and continue doing next sprint.
Write one point per note and keep it short.
When the timer goes off, one person should set a timer for 1 minute and group the notes into themes.
Next, set a timer for 2 minutes and all vote on the most important themes by adding a dot or a +1 to the note.
Finally, set a timer for 8 minutes and all discuss the top three themes.