🏷️ backlog

Module-The-Launch 🔗

Ask a technical question 🔗 Clone

https://curriculum.codeyourfuture.io/guides/getting-help/asking-questions/

Why are we doing this?

When you hit a blocker, write up your blocker as a technical question. You can write this directly in Slack or on a ticket on your board and then link it in Slack. The process of writing out your blocker is key to resolving it.

📝 Note

Before asking a question Make a prediction and explain why you think that will happen Run the code Compare your prediction against what actually happened

Now, write up your mental model using this format:

What I did What I expected What actually happened

How to submit

Post your question in Slack

How to review

Before asking a question check in with yourself and make sure you have done the following:

I have…

  • Done some research myself
  • Explained what I’ve already tried to solve my problem
  • Stated what I expected, why I expected it, and the actual results
  • Formatted my code
  • Checked my spelling and grammar
  • Pasted the exact, complete error message, if there is one
  • Read my whole question carefully to make sure it makes sense and contains enough information for someone coming to it without any of the context that I already know?

After you’ve asked your question

I have checked…

  • Are you monitoring your questions and replying to people giving their time to help you?
  • Have you been asked for a Minimum Reproducible Example?
  • Have you posted an easy to understand answer to your questions that includes everything you learnt
  • :brain: Prep work
  • 🎯 Topic Communication
  • 🎯 Topic Problem-Solving
  • 🏕 Priority Mandatory
  • 🐇 Size Small
  • Week 1
  • Week 2
  • Week 3
  • Week 4
[PD] Weekly Catch-up 🔗 Clone

Coursework content

Go to your weekly catch-up and reflect on it

Estimated time in hours

1

What is the purpose of this assignment?

  • Participate in the weekly catch-up.
  • Reflect on how the meeting went for you. For example: Could you have said something differently? Should you have asked any other questions? What did you like and not like most in it? What have you learned?

How to submit

  • Add a short 50-100-word reflection as a comment on this GitHub issue.
  • Make sure it is reviewed with Grammarly or similar. You should have no grammar mistakes.

Anything else?

N/A

  • 🏕 Priority Mandatory
  • 🐇 Size Small
  • Week 1
  • Launch
[PD] Fill in your team data on the trainee tracker 🔗 Clone

Coursework content

One important metric we mentioned in preparing this sprint is the trainee tracker. A file for your cohort will be created. Check your cohort channel, and if it isn’t available, ask the volunteers about it. Only one of the team members has to do this task.

Estimated time in hours

0.5

What is the purpose of this assignment?

Ensure your team can be measured correctly during the Launch module

How to submit

Read notes on the titles of each column to understand which data you need. Add the correct data about your team on the spreadsheet. Let your team know that this has been done Share the link to the trainee track on this issue

Anything else?

N/A

  • 🔑 Priority Key
  • 🦔 Size Tiny
  • Week 1
  • Launch