🏷️ backlog

Module-User-Focused-Data πŸ”—

[TECH ED] πŸ“ Code review πŸ”— Clone

Why are we doing this?

Code review is an essential part of self-evaluation. Get a code review for a piece of work; then reply and iterate on this feedback.

You can also use any solutions to review your code independently.

Maximum time in hours

1

  • πŸ• Priority Mandatory
  • πŸ“… Sprint 3
  • :memo: Self evaluate
[TECH ED] πŸ«±πŸ½β€πŸ«²πŸΏ Pair program πŸ”— Clone

Instructions

  1. Pair up with a volunteer and work on a kata together
  2. As a trainee, you will need to explain your thought process, plan out what to do, write the code and check it works
  3. Volunteers will need to ask questions to check your understanding, provide guidance if you stuck, give honest and meaningful feedback

🧭 Guidance for volunteers

  • Don’t take over! It’s important trainees get used to figuring things out. Provide guidance and assistance but trainees need to struggle to overcome any obstacles with understanding and technical communication
  • Give honest feedback. Trainees can’t develop if they don’t receive honest feedback about their progress.
  • Ask questions. Sometimes asking a clarifying question can help learners discover errors and often promotes more thoughtful responses.
  • Encourage best practices. Reinforce good practices like reading error messages carefully sessions and checking documentation.

Why are we doing this?

Pair programming is an excellent way to develop programming and communication skills. It is often much easier to work through something when working on something 1 to 1. It is also helps our trainees to prepare for technical interviews when they’ll need to code in front of other people.

Acceptance criteria

  • You have pair programmed on a kata with a volunteer for at least one hour
  • πŸ• Priority Mandatory
  • πŸ‡ Size Small
  • πŸ“… Sprint 3
  • :memo: Self evaluate
[TECH ED] Front End Practice πŸ”— Clone

https://www.frontendpractice.com/

Why are we doing this?

This useful site has a series of projects you can do to keep your front end skills in shape all the way through the course. Use all the skills you’ve developed in wireframing, decomposition (breaking down websites into components), testing and iteration to produce some great looks for your portfolio.

Maximum time in hours

0

How to get help

Share your blockers in your class channel. Use the opportunity to refine your skill in Asking Questions like a developer.

How to submit

No submission step. Put good ones in your portfolio.

  • 🎯 Topic Communication
  • 🎯 Topic Delivery
  • 🎯 Topic Iteration
  • 🎯 Topic Problem-Solving
  • 🎯 Topic Programming Fundamentals
  • 🎯 Topic Requirements
  • 🏝️ Priority Stretch
  • πŸ‚ Size Medium
  • πŸ‹ Size X-Large
  • πŸ“… HTML-CSS
  • πŸ“… Sprint 3
[TECH ED] Play the CLI Treasure Hunt πŸ”— Clone

https://github.com/CodeYourFuture/Project-CLI-Treasure-Hunt

Why are we doing this?

Alongside learning web development, you need to become familiar with the basics of the command line. The command line is how you talk directly to your computer, instead of pointing and clicking at areas on a screen to trigger actions.

All interfaces are limited sets of possible interactions with data, arranged in ways (with words, colours, pictures, pixels) to guide the user towards the information they want. Clicking a link on a screen is really no different to typing. In both cases you are changing to a new directory. The difference is only in the interface you use to issue the command. Do not confuse the method with the goal.

I really want you all to understand this deeply and think about it many times over the course of your career. Do not decide you are “front end” or “back end” or limit your understanding in these ways. A CLI is an interface. An API is an interface. A GUI is an interface. All interfaces are maps. It’s how we travel around data to find what we need.

The map is not the territory.

Maximum time in hours

1

How to get help

Share your blockers in your class channel.

How to submit

  1. Clone the repo https://github.com/CodeYourFuture/Project-CLI-Treasure-Hunt
  2. Open the folder in VSCode
  3. Open the terminal inside VSCode
  4. Type node clue.js to start

The submission clue is inside the treasure hunt.

Anything else?

Completely optional cultural background reading: In the Beginning was the Command Line ~ Neal Stephenson, 1999

  • 🎯 Topic Communication
  • 🎯 Topic Programming Fundamentals
  • 🎯 Topic Structuring Data
  • πŸ• Priority Mandatory
  • πŸ‡ Size Small
  • πŸ“… HTML-CSS
  • πŸ“… Sprint 3
[PD] Learn how to use Google Doc and Slides πŸ”— Clone

Coursework content

  1. Go to https://g.co/AppliedDigitalSkills
  2. Click “Sign in” in the top right
  3. Sign in with your Google account, or create a new one
  4. Click “I am a student”
  5. Click “Join a class” and enter class code: qchyyg
  6. Start the Communicate Effectively at Work course
  7. Do lessons “4 - Communicate Ideas in a Proposal” and “5. Present Information About Your Job”

Estimated time in hours

1

What is the purpose of this assignment?

The goal is for you to be comfortable using Google Docs and Google Slides, which you will use a lot in your professional life.

How to submit

Share the results to the exercises of both lessons on your coursework board.

  • πŸ• Priority Mandatory
  • πŸ‡ Size Small
  • πŸ“… HTML-CSS
  • πŸ“… Sprint 3
[PD] Developing a growth mindset πŸ”— Clone

Coursework content

Watch The power of believing that you can improve | Carol Dweck | TED and Neuroplasticity. Write your reflections on why it is important to have a growth mindset as a developer and how a growth mindset will positively impact you in your career in the long term. Try to answer the following questions:

  • When did I have a closed mindset this week, and why?
  • When did I have an open mindset this week, and why?
  • What have I learnt about myself, as a result?
  • What will I do differently next time?

Estimated time in hours

1

What is the purpose of this assignment?

This assignment supports developing a growth mindset while learning new skills and facing barriers.

How to submit

Write in your cohort’s Slack channel what actions you will take in order to overcome your barriers to participating in live coding and write a supportive message to one of your peers who have shared their barriers in the channel. Share the screenshot of your post on your ticket.

  • πŸ• Priority Mandatory
  • πŸ‡ Size Small
  • πŸ“… HTML-CSS
  • πŸ“… Sprint 3
[PD] Reflect on your development so far πŸ”— Clone

Coursework content

You have now learned many new things: tools, skills, and programming language. Considering this, reflect on your development.

Estimated time in hours

0.5

What is the purpose of this assignment?

Reflect and celebrate how much you have developed your knowledge so far.

How to submit

  1. Think about 1 achievement you had and 1 professional skill (not technical skill) you still want to develop.
  2. Write a paragraph about these two: what are they AND why do you think you did well OR still have to learn them?
  3. Share this with your class on the thread about this coursework. If the thread doesn’t exist yet, you are the first and can create it
  4. Read your fellow trainees’ messages and react to them with emojis that support them or are relevant to their content.
  5. Copy the link to the Slack message you posted on this ticket
  6. Copy a screenshot of the message you posted on this ticket
  • πŸ• Priority Mandatory
  • πŸ¦” Size Tiny
  • πŸ“… HTML-CSS
  • πŸ“… Sprint 3
[PD] Review your Plan to build a Life as a Developer πŸ”— Clone

Coursework content

As mentioned in the beginning, this is not an exercise that can be done once.

So write down:

  • Did you manage to implement any changes? Why?

Also, reflect and write down:

  • How are these changes affecting your weekly hours?
  • Do you now have more or less energy?
  • More or less time?
  • Do you feel happier or not?
  • Are you feeling more or less anxious?
  • Can you sleep and rest better or not?
  • Do you feel your focus level has changed?

Estimated time in hours

0.25

What is the purpose of this assignment?

Review your Build your Life plan, to ensure you are thinking about it and acting to make changes.

How to submit

Add a comment with the updated links OR explain why you haven’t made any changes.

  • πŸ• Priority Mandatory
  • πŸ¦” Size Tiny
  • πŸ“… HTML-CSS
  • πŸ“… Sprint 3
πŸ§‘πŸΎβ€βš–οΈ Check module success criteria πŸ”— Clone

https://programming.codeyourfuture.io/user-data/success/

Why are we doing this?

πŸ”‘ The most important thing is that you are secure in your understanding.

At the end of the course, we will expect you to build novel applications using your understanding. If you cannot build things, we cannot put you forward for jobs. It is in your personal interest to make sure you have properly understood this module.

To progress to the next module you need to meet the success criteria for this module. How will you as a cohort meet the module success criteria? Discuss it in your class channel and make a plan together.

πŸ§‘πŸΏβ€πŸŽ€ Good strategies

  • Asking volunteers to review your code
  • Helping each other with coursework blockers
  • Arranging midweek study sessions
  • Using Saturday time to review code and cohort tracker

πŸ™…πŸΏ Bad strategies

  • Opening empty PRs
  • Copying and pasting
  • Breaking the Trainee Agreement
  • Mistaking the measure for the target

Maximum time in hours

.5

How to get help

Discuss with your cohort. Support each other.

How to submit

At the end of your module you will need a representative to report to the organisation. Here’s your template, fill in your details and delete as appropriate:

πŸ“ˆ Cohort Progress Report from @cohort-name to @programme-team

  • criterion
  • criterion
  • criterion
  • criterion

βœ… We are progressing to the next module. β›” We are taking a consolidation week to meet our targets.

  • 🎯 Topic Code Review
  • 🎯 Topic Communication
  • 🎯 Topic Delivery
  • 🎯 Topic Requirements
  • 🎯 Topic Teamwork
  • 🎯 Topic Testing
  • 🎯 Topic Time Management
  • πŸ• Priority Mandatory
  • πŸ¦” Size Tiny
  • πŸ“… HTML-CSS
  • πŸ“… Sprint 1
  • πŸ“… Sprint 3