Coursework content

GitHub Projects are how we manage our workload at CYF. We use Kanban, an agile project management methodology that visualises workflow, work progress, and focuses on continuous improvement.

Kanban is used by many tech companies worldwide, so the more you use it, the better prepared you will be when you get your job in tech.

Estimated time in hours

0.25

What is the purpose of this assignment?

1. Watch the videos How to use your Github Project
2. Video about the different tabs on the Project and prioritising your work
3. How to use filters

How to submit

No submission needed

Anything else?

These are links if you want to understand more about:

• GitHub Projects
• What is Kanban

Coursework content

If you are here, it means you want a job in tech. But coding is not the only skill you must have to get a job. Professional skills are as important.

But what is the primary goal of people that work in tech? We build Digital Products. And they are built with various roles, such as Sofware Developers, UX Designers, Testers, Product Owners/ Managers, and Scrum Masters.

Research the professional skills needed for every role mentioned above and write three sentences describing these skills and why they are important.

For example: Software Engineers must be able to work collaboratively with all team members, so conflicts can be reduced.

Estimated time in hours

1

What is the purpose of this assignment?

1. Your research must be made available using Google Docs. We expect 3 phrases for every role, so at least 15 phrases in total. (20 min)
2. Review your grammar using any available tool, such as Grammarly. You should not have more than (10 min)
3. Share your document on the “Professional Skills research” thread on your cohort Slack channel. If the thread doesn’t exist yet, create it. (5 min)
4. Choose 2 people’s research that has yet to be read. When you start reading it, add the 👀 emoji to their thread so everyone knows you are reading it. (2 min)
5. Read their content and add at least 1 comment on each Google doc. (20 min)
6. When you have read someone’s research, react with an appropriate emoji to their post on Slack so they know you’ve done it. (2 min)

How to submit

1. Add the link to your post on Slack on this coursework
2. Add a screenshot of your post on this coursework
3. Add the link to your Google Doc on this coursework. Make sure the link gives permission to comment on the document directly.

Anything else?

• How to create a Google Docs: suggested video.
• How to comment on Google Docs: suggested video
• You can use job descriptions to identify the non-technical skills employers seek. Some good resources are CW Jobs, Linkedin, Indeed, or any job board.

Coursework content

https://syllabus.codeyourfuture.io/fundamentals/preparation/tips

Estimated time in hours

1

What is the purpose of this assignment?

REMEMBER YOUR GOAL

The goal is not to complete the exercise. The goal is to learn.

How to submit

1. Read the Tips for Success page.

2. Join or create a thread in your cohort Slack channel to discuss how you will apply them.

Coursework content

Go to this link to understand how you learning helps you to learn:
https://css-tricks.com/learning-to-learn/

Estimated time in hours

.5

What is the purpose of this assignment?

You can use your Github project board to structure your learning like Sarah’s. Create your own issues for blocks of learning and schedule them into your week.

Then I take all of those features, write them out, and estimate how much time I’ll need for each one. Here’s an example where I wrote out all the things I needed to learn. The yellow numbers on the side are my time estimates in half hour units.

• You can use task lists on issues
• And check them off
• When you’re done

How to submit

• Create your own ticket with your own learning goals.
• Add it to this coursework to be reviewed

Link to the coursework

https://blocks.codeyourfuture.io/

A note on ordering

This exercise should be done after the Code.org coursework in the same sprint. The reason for this is that the Code.org course will give you skills which will help you with this coursework - this coursework depends on the other coursework.

In the future, we won’t always call out dependencies between coursework - just like in real life as a software engineer, part of your sprint planning is about working out the best order to do different tasks. When planning, you should consider what the best order of approaching tasks will be.

Why are we doing this?

In this course, you will use block-based programming (CYF Blocks) to create JavaScript that changes the HTML on a web page. Work through the exercises in order, up to and including Buttons, inputs and clicks: a todo list.

You must at least attempt all those exercises before we meet. If you get stuck, don’t worry. Come to the session with your questions and we will all discuss them together.

Maximum time in hours

8

How to get help

If you get stuck, don’t worry. Come to the session with your questions and we will all discuss them together.

How to submit

Once you’re finished, share your solution to List of links by pasting the (very long!) url onto a comment on your copy of this ticket.

Copy one URL per comment.

How to review

Share your solution on with your cohort on your cohort’s slack channel and ask for critique.

Anything else?

If you have extra time, complete one of the exercises in Buttons and Clicks: consolidation (or create something entirely new) and share it with your cohort in the Slack channel.

Write down some questions to bring up next week.

Link to the coursework

https://studio.code.org/s/course3/lessons/2/levels/1

Why are we doing this?

Code.org is a website which teaches beginners how to code and gives them lots of practice. It uses block-based coding. Don’t be put off by the simplicity: Harvard University teaches block-based coding. The concepts covered here are some foundational principles of programming that you will need to understand our application, CYF Blocks.

As we will be doing most of our coding in CYF blocks, you only need to do up to Lesson 12, . It’s important to spend some time with these ideas to prepare yourself for CYF Blocks.

To get set up:

1. Use the account you made during your class preparation.
2. Start by clicking on item 1 from lesson “2. Maze”. (Yes, you should skip lesson 1)

If you get stuck, discuss in your cohort’s Slack channel. Hitting blockers is normal in coding and talking through the problem is a good strategy.

Read the instructions carefully and complete all stages of these lessons:

Lesson 2 - Maze
Lesson 3 - Artist
Lesson 5 - Artist: Functions
Lesson 6 - Bee: Functions
Lesson 7 - Bee: Conditionals
Lesson 8 - Maze: Conditionals
Lesson 11 - Artist: Nested Loops
Lesson 12 - Farmer: While Loops

You can skip all of the lessons starting with “Unplugged Activity”.

Maximum time in hours

4

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

Once you’re finished, take a screenshot and attach it to your copy of this ticket on your own planning board. Then move your copy of this ticket to “Done” on your own planning board.