🧑🏽‍🤝‍🧑🏽 day-plan

🔖
  1. Energiser
  2. City Guide Pair Programming
  3. Lunch
  4. Study Group
  5. Code Review
  6. Afternoon break
  7. Value And Work Not Done
  8. Set up Render
  9. Retro

✍🏽 Register

Energiser

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.

  1. Traffic Jam: re-order the cars to unblock yourself
  2. Telephone: draw the words and write the pictures
  3. 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.

City Guide Pair Programming 🔗

Node Challenge - London Mini-Guide

In this challenge you are going to build a full stack application (server & client) that shows the number of hospitals, doctors, pharmacies and colleges in some of London’s boroughs.

This exercise is designed to develop your pair programming skills and to get you thinking about how to design a full stack application. You’re not expected to get everything completed.

Server

The Server Challenge

Client

The Client Challenge

Time to Complete

This challenge has three levels. Budget one hour to complete the first level. If you have more time, do more levels.

Instructions

Split into groups of two or three people.

One person will start as the driver (typing the code) and the others will begin as the navigators.

You must complete the first level before moving on to the second level. Do not jump around.

Begin with the server challenge.

Live Version:

https://london-mini-guide-challenge.netlify.app/

project screenshot

Data Source

The data is provided to you in a folder ./data which contains 3 files: Harrow.json, Heathrow.json and Stratford.json.

Each file in this format:

{
    "pharmacies" : [
        {
            "name" :
            "address":
            "website":
            "phone" :
        }
    ],

    "colleges" : [
        {
            "name" :
            "address":
            "website":
            "phone" :
        }
    ],

    "doctors" : [
        {
            "name" :
            "address":
            "website":
            "phone" :
        }
    ],

    "hospitals" : [
        {
            "name" :
            "address":
            "website":
            "phone" :
        }
    ]
}

Data source: https://www.yell.com/

Data has been collected using a technique called web scraping.

Optionally, to know more about web scraping, check out these resources:

‌

Community Lunch

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.

Study Group

Learning Objectives

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.

NW6 | Hadika Malik | Module Servers | Mailing List API project | 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. I have completed the CRUD requests.

Questions

Ask any questions you have for your reviewer.

Start a review
NW6 | Rabia Avci | Module Servers | [TECH ED] Mailing list API Project | 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.

I created a server, served my app through it. Also created middlewares, routes, utils folders for better documentation.

Questions

Ask any questions you have for your reviewer.

Start a review
WM5 | AISHA_ATHMAN_LALI | MODULE_SERVERS | WEEK_2 | CHAT_SERVER | LEVEL-1-2-3 🔗

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

This is a PR on a chat server project. I have attempted until level 3.

Start a review
NW6 | Fikret Ellek | Module Servers | [TECH ED] 🏝️ Stretch challenges / 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.

I have created enpoints for reviewing, creating and deleting booking data. Tried to separate functions from server file to a specific functions folder.

Questions

Ask any questions you have for your reviewer.

Start a review
WM5| AISHA_ATHMAN_LALI | MODULE_SERVERS | WEEK_1 | QUOTE_SERVER 🔗

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

This is a PR for Quote Server API Project.

Start a review
See more pull requests

Afternoon Break

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.

Value and Work Not Done

Learning Objectives

Preparation

Do the prep.

Introduction

Building a product that has value is crucial. It’s relatively easy to just create something, but doing it well is a different story. It’s important to understand what and why you are building something and for whom. If not, you are just wasting your and your client’s time.

Value Measurement Chain

🎯 Goal: To practice identifying the stages of the value measurement chain. (25 minutes)

Work in teams of 3-4 people.

Assign which stage of the value measurement chain (Input - Effort - Output - Outcome - Impact) relates to each of the following measures:

  • Number of product releases to the customers every month.
  • Count of person-days spent on a task.
  •  Lines of code in a pull request.
  •  Response to a marketing vision for a feature from social media.
  • Venture capital investment in the company, based on a product vision.
  • Family and social connections are enhanced because a communication feature is used well.
  • Refactoring because a feature was badly implemented.
  • Persuading other people to finish their tasks enables you to begin yours.
  •  The system can display calories burned during activity logged.
  •  Reduced medical interventions due to healthier lifestyles encouraged by the exercise app.
  • A user knows an estimate of calories burned by exercise.
  • Release to market of location tracking software version with calorie counter feature. 
  • Opportunity cost / future value of food intake forecasting for diabetic users of that location tracking software.

Tip for timing: Use the first 10 minutes to assign items in your group, then during the last 15 minutes discuss each item in the class.

Work Not Done

🎯 Goal: To practice identifying which tasks should/shouldn’t be done and why. (35 minutes)

Work in teams of 3-4 people.

Take 25 min to complete this part of the exercise:

  1. Suggest which of the following items should not be done. 
  2. Define what would change the decision.
  3. What would make it more valuable?
  4. What would make it less valuable?
  • Fixing a security vulnerability in the latest version of the product, where any user could impersonate any other in a REST call.
  • Fixing a security vulnerability in an old version, which is at “end of life”, but the customers have to pay to upgrade.
  • Refactoring technical debt affects a few possible enhancements to a rarely used feature.
  • Fixing a spelling mistake on the website in a prominent place.
  • Adding a major new feature, which some users think would be great, but most users don’t care about.
  • Adding a new feature when the next item on the backlog is to fix a common bug.
  • Writing a definition of done with the team so everyone shares expectations of documentation, testing, etc.
  • Redesigning the UI workflow to present questions in the same order a person would think about them.
  • Re-implementing an existing feature that works but looks a bit dated.
  • Holding meetings with several customers to clarify the impact of a certain bug on them.
  • Refining and estimating items on the backlog will probably be in the sprint after next.
  •  Add and remove database table columns to comply with the architect’s new policy.
  •  Fixing bugs in an experimental prototype feature for which we are already collecting A/B test analytics.

Go through each task in the class and ask the questions listed at the beginning. It’s alright if you don’t have time to cover all tasks.

Tips for timing: 15 minutes to work on the exercise in groups, 20 minutes to discuss.

Set up Render

Learning Objectives

Let’s try out using Render to host our Node.js application. There are many platforms that you can use to host your Node.js application, but we’re using Render right now because it’s free. If your cohort has found a better option, please use that, and contribute your setup guide back to the curriculum.

Set up Render

  1. Fork https://github.com/CodeYourFuture/CYF-React-Express-Template
  2. Create an account with Render and choose GitHub as your auth.
  3. Create a new Web Service and choose Build and deploy from a Git repository
  4. Connect your forked repo to Render

Retro: Start / Stop / Continue

  Retro (20 minutes)</span>