π·οΈ backlog
Module-Structuring-and-Testing-Data π
[CYF] π‘ Do you need support to continue studying? π Clone
βοΈ Enrol as a Trainee
Have you finished Module 1 of ITP? Well done! πͺ
If you need help with transport, childcare, data, or a laptop to keep studying, apply to enrol as a Trainee . Trainees at CYF can claim expenses to support their studies.
Want to know more? Apply to enrol as a Trainee
β¨ Code Your Future
- π Sprint 1
[TECH ED] Complete Sprint 1 exercises π Clone
Link to the coursework
https://github.com/CodeYourFuture/Module-Structuring-and-Testing-Data
Why are we doing this?
These challenges are designed to develop your ability to read and understand documentation, and to read and interpret error messages.
Maximum time in hours
6
How to get help
Share your blockers in your class channel https://curriculum.codeyourfuture.io/guides/asking-questions/
How to submit
- Fork to your GitHub account.
- Make a branch for this project.
- Make regular small commits in this branch with clear messages.
- When you are ready, open a PR to the CYF repo, following the instructions in the PR template.
There are several projects in this repo. Make a new branch for each project.
- π Priority Mandatory
- π¦ Size Large
- π JS1
- π Sprint 1
[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.
We’re using GitHub Labels in our Code Review process. In order for a volunteer to review your pull request, you will need to add a “Needs Review” label to it.
- Open your pull request
- In the right sidebar, click Labels, then select “Needs Review”
Take a look at our code review process from beginning to end. Let us know if you have any questions or need help!
You can also use any solutions to review your code independently.
Maximum time in hours
1
- π Priority Mandatory
- π Sprint 1
- :memo: Self evaluate
[TECH ED] π«±π½βπ«²πΏ Pair program π Clone
Instructions
- Pair up with a volunteer and work on a kata together
- As a trainee, you will need to explain your thought process, plan out what to do, write the code and check it works
- 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 1
- :memo: Self evaluate
[TECH ED] Codewars π Clone
Link to the coursework
https://www.codewars.com/users/CodeYourFuture/authored_collections
Why are we doing this?
Every week you need to complete at least three kata. Spend at least 20 minutes, three times a week, on your kata workout.
Find the Collection for this module on the CodeYourFuture account.
Take some time to check your levels. Before you are accepted on the jobs programme, you need to reach a Level 5 kyu in Codewars. Are you on track to reach this standard? Have you run a study group to work on kata? Have you reached out on the #cyf-codewars channel? What is your plan to meet this goal?
Maximum time in hours (Tech has max 16 per week total)
1
How to get help
- Join the #cyf-codewars Slack channel
- Read the CYF Codewars docs
- Read Codewars advice from CYFers
- Read Codewars advice from mentors
Remember, after 20 minutes, take a break.
How to submit
Your codewars progress is tracked automatically and is available on the public API. You don’t need to submit it.
How to review
Once you have completed your kata, look at the other solutions in the solutions view. Consider how many different approaches there are.
- π― Topic Code Review
- π― Topic Problem-Solving
- π― Topic Programming Fundamentals
- π― Topic Requirements
- π― Topic Time Management
- π Priority Mandatory
- π Sprint 1
- π JS2
[TECH ED] CIP Intro to Python π Clone
Link to the coursework
https://codeinplace.stanford.edu/public/studenthome
Why are we doing this?
Get introduced to Python. Learn about the print and input statements. Also learn about variables and types, including int, float, and string. Get started writing your first few Python programs that use these statements.
Then, learn about mathematical expressions in Python, including arithmetic operators and rules of precedence for evaluating expressions. Also learn about type conversion and the use of constants in programs. Review the Python math and random libraries for mathematical functions and random number generation, respectively. Get practice putting these concepts together in sample programs.
Maximum time in hours
6
How to get help
Come to Slack and CYF coworking spaces with your blockers.
- π― Topic Programming Fundamentals
- π Priority Mandatory
- π¦ Size Large
- π Sprint 1
[PD] Writing an email for an internship π Clone
Coursework content
Draft an email to apply for an internship at a fictional company called Vonda. Make sure to include the five things below:
- Why you want to become a software developer
- Your background and your past
- What you are doing at the moment
- Where you see yourself in the future
- Why Vonda should give you the opportunity to do an internship
The email should be formatted in a way that is ready to be sent. Make sure you include a subject title and pay attention to the formatting (font type and size, alignment etc).
Estimated time in hours
1
What is the purpose of this assignment?
This assignment aims to improve your writing skills.
How to submit
Share the link to the Google doc on the ticket on your coursework board.
- π― Topic Communication
- π Priority Mandatory
- π Size Small
- π JS1
- π Sprint 1
[PD] What do you think? π Clone
Coursework content
Use critical thinking skills to answer a clientβs request on a web page you developed.
Estimated time in hours
1
What is the purpose of this assignment?
A client requested the navigation bar at the bottom of their web page. Research what best practice is and why this would be a good, a bad or a neutral idea.
These are the tips to help you write it:
- Provide appropriate and sufficient arguments and examples
- Research arguments against and for the statement before coming to your conclusions.
- Choose terms that are precise, appropriate, and persuasive
- Make clear the transitions from one thought to another to ensure the overall logic of the presentation
How to submit
- Create a text with at least 250 words.
- Make sure your text is reviewed by a grammar tool. It should have at most 3 mistakes.
- Add the link to the Google doc to comment on this issue. Make sure it is open for anyone to comment.
- π Priority Mandatory
- π Size Small
- π JS1
- π Sprint 1
[PD] Review your development plan π Clone
Coursework content
Using the Build Your Life plan and your first version of your Career Development plan, we want you to continuously think about the goals you want to achieve: short/medium/long-term. These should still be linked to the areas you want to develop.
Remember: 2-3 areas are enough to change in such a short time, so it’s better to focus on a few, get them nailed, and then choose another area.
Ensure you are not only thinking of technical knowledge you want to acquire but especially skills and processes that will help you become a developer.
Examples of goals
- Short term: Practicing coding = Code 1 hour a day on weekdays
- Medium-term: Enhance my written English = Trying to correct by myself the errors that the automated grammar tool is showing in my text
- Long term: Get a job in tech = Send 1 tailored CV per day when I have graduated from Code Your Future
Estimated time in hours
0.5
What is the purpose of this assignment?
Define where you want to be in the short, medium and long term. This helps give you perspective and clarity of where your direction is and if you are doing the right things to get there.
How to submit
- Share your development plan link as a comment, open to anyone to comment
- Write a paragraph, as a comment on this issue, about what you have learned/changed
- π Priority Mandatory
- π Size Small
- π JS1
- π Sprint 1
π§πΎββοΈ Check module success criteria π Clone
Link to the coursework
https://programming.codeyourfuture.io/structuring-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
- π JS1
- π Sprint 1