πŸ“… backlog

Module-HTML-CSS πŸ”—

[PD] Feeling, behaving and acting like a professional in the software industry πŸ”—

Coursework content

You are back to your Plan your Life as a Developer.

This plan is not something that you can finalise in a short period. You’ll need to go back to it a few more times if you’d like to find an honest description of your current week and identify the necessary changes to it.

As a week will have passed since you did it, you can compare what you wrote with the reality of the week that passed.

Reflections on your current plan.

  • How much energy did you have when you sat down to study and work on CYF projects?
  • How tired or distracted were you?
  • How many interruptions did you get?

Other areas to reflect:

  • On your work (or other studies), did you work longer hours than what you planned? What happened?
  • Were there any activities that you dedicated more time to it than what you expected?
  • How is your sleep?
  • Do you manage to feel rested in the morning?
  • How do you start your day?

Reflecting on this, think about these two topics:

  1. What changes you might need to bring to your life.
  2. Define their short/medium/long-term goals.

Then:

  • Add these two items to your existing Google Doc. (Reminder: minimum 50 words each and reviewed with an automated grammar tool)
  • Share them with your pair.
  • Discuss with them, so you can identify anything that is missing, if what you are planning is realistic, or if it is just right.

Estimated time in hours

1.5

What is the purpose of this assignment?

You are getting a deeper understanding of what blockers and distractions that hold you up. But now, you also have to start thinking about what can you do to change this situation and what goals can you start putting in place.

How to submit

Add a comment to this issue with:

  • The link to this document is a comment on this issue. Make sure anyone can comment on it.
  • An explanation of what was discussed with your pair.
  • πŸ‚ Size Medium
  • πŸ”‘ Priority Key
  • πŸ“… Week 2
[PD] Create your Development Plan πŸ”—

Coursework content

You will create your own Development Plan, starting with these questions:

  1. What are your blockers?
  2. How can you plan your time so that you can do your developer work?
  3. Is this plan sustainable until you find a job (which might not be straight after graduation)?
  4. How can you be a developer every day?

Work with your pair to ask and give feedback on your development plan

  • The feedback can be discussed in person or in a Slack huddle first
  • Then add your feedback for your pair and their feedback for you on this ticket

Estimated time in hours

1

What is the purpose of this assignment?

To practice active listening by developing and sharing a Development Plan. To practice effective listening behaviours and see the benefits of active listening and how it makes us better communicators.

How to submit

Add the following to this ticket:

  • The link to your development plan. Use this template.
  • The screenshot of your feedback for your pair
  • The screenshot of your pair’s feedback for you

Anything else?

The Development Plan is not a one-off exercise. It is a plan you should review constantly with your new knowledge and when you have developed new skills. Search for “development plan template” online and choose the one that fits you best.

  • 🎯 Topic Problem-Solving
  • 🎯 Topic Time Management
  • πŸ‚ Size Medium
  • πŸ“… HTML-CSS
  • πŸ“… Week 2
[PD] Active listening techniques πŸ”—

Coursework content

Read the active listening techniques article and reflect. Write a 250-word essay on your own listening habits, challenges and improvement goals.

Estimated time in hours

1

What is the purpose of this assignment?

This assignment will improve your listening and writing skills.

How to submit

Share the link to your Google doc on the ticket on your coursework board.

  • 🎯 Topic Communication
  • πŸ• Priority Mandatory
  • πŸ‡ Size Small
  • πŸ“… HTML-CSS
  • πŸ“… Week 2
[TECH ED] Play the CLI Treasure Hunt πŸ”—

https://github.com/CodeYourFuture/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 cd Clues/Where . 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 git@github.com:CodeYourFuture/CLI-Treasure-Hunt.git
  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?

In the Beginning was the Command Line ~ Neal Stephenson, 1999

  • 🎯 Topic Communication
  • 🎯 Topic Programming Fundamentals
  • 🎯 Topic Structuring Data
  • πŸ• Priority Mandatory
  • πŸ‡ Size Small
  • πŸ“… HTML-CSS
  • πŸ“… Week 2
[TECH ED] Prep work for live session πŸ”—

https://curriculum.codeyourfuture.io/html-css/sprints/2/prep/

Why are we doing this?

You might be used to school environments where you attend a lecture or class and then are given homework or tests to show you heard or understood the lecture. We don’t do that at CYF as we have found it doesn’t prepare people well for a good job in tech.

As a tech professional, you won’t be told a series of answers and then asked just to demonstrate your understanding/recollection of them! That will never happen! There’s no business value there at all. As a tech professional, your job will be to ask good questions, research new ideas, and figure out solutions to unsolved problems. So let’s start this now.

The prep work here will introduce you to new concepts for the week. If you already have all these concepts, you need to identify something else in your coursework to bring because everyone is expected to come to class with questions.

Find this week’s blockers thread in your cohort channel and add your question to it.

Maximum time in hours

3

How to get help

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

  • 🎯 Topic Programming Fundamentals
  • 🎯 Topic Requirements
  • πŸ• Priority Mandatory
  • πŸ‚ Size Medium
  • πŸ“… HTML-CSS
  • πŸ“… Week 2
[TECH ED] Module Project: Store Page πŸ”—

https://github.com/CodeYourFuture/HTML-CSS-Module-Project/tree/master/level-2

Why are we doing this?

Thinking back to Fundamentals, we develop products through iteration. We don’t build everything all at once, we add features over time. So let’s embed that practice now by:

  1. extending the homepage by adding a new block to it.
  2. adding a new store page that allows users to buy a Karma device using an order form.
  3. connecting the 2 pages together by adding navigation

You are NOT required to make this page work on mobile devices! ;)

Stretch goals

The radio buttons and checkbox in the design require some advanced CSS to follow the design while still using the native functionality of these inputs. Try and give it a go, but don’t lose sleep over it if you don’t manage! This is challenging and will require some research.

Maximum time in hours

8

How to submit

  • Remember to commit and push your code often. Don’t git add . Make sure you know what you are putting in your codebase.
  • Once you’re ready for review, do a final push and create a Pull Request.

Note: If you’ve added your code to the same branch you were using last week, then it will just update your original Pull Request and you won’t need a new PR.

How to review

  1. Ask for review from a classmate or mentor, clearly describing what you are looking for
  2. Make changes based on their feedback
  3. Review and refactor again next week

Anything else?

You’ll find the designs at the following Figma links:
HOMEPAGE - New section: https://www.figma.com/file/BPtLAPr1HhwQdNfxGyFouo/Karma-design?node-id=23%3A0
STORE - New page: https://www.figma.com/file/BPtLAPr1HhwQdNfxGyFouo/Karma-design?node-id=858%3A3

  • 🎯 Topic Iteration
  • 🎯 Topic Requirements
  • πŸ• Priority Mandatory
  • πŸ¦‘ Size Large
  • πŸ“… HTML-CSS
  • πŸ“… Week 2
[TECH ED] Design Basics πŸ”—

https://scrimba.com/learn/design

Why are we doing this?

Runtime 1 hour 8 minutes.

This course will help you with your Cake project, and give you some fundamentals of design to help you interpret and express design as code.

Maximum time in hours

1.5

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

  • 🎯 Topic Problem-Solving
  • 🎯 Topic Requirements
  • 🏝️ Priority Stretch
  • πŸ‚ Size Medium
  • πŸ“… Week 2