Ask a good question for real

Open
#11 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Domain
content, documentation

Research direction

Start with the Learning Objectives and the linked Asking Good Questions Guide. Complete the Slack question and peer-feedback activities, then add screenshots of your question and feedback to comments on this issue as evidence of completion.

Written by the indexing model from the issue text.

Description

🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 2 Core Module-Structuring-And-Testing-Data Submit:Issue
Learning Objectives
  • Ask a meaningful, well-structured question on Slack
  • Answer a question on Slack appropriately
  • Give feedback to colleagues when they ask questions
Why are we doing this?

You need to practice any skills to get good at them. Your task is to ask your cohort a “Good Question” on the Slack channel when you next have a genuine issue you need help with.

Remember:

  • Identify one problem at a time to ask about
  • Say what research you’ve already done to try and resolve the problem yourself
  • Be specific about the problem
  • Be polite and respectful of the person you are asking.
  • Be concise (minimal reproducible example) - only give the relevant code snippets or errors messages
  • Choose who to ask based on their general expertise, availability, distance from you in the team or who you haven’t asked before.
  • Refer to documentation, other code, and discussions with specific links.
  • Show what happens when you try your solution.
  • Explain what you expected or wanted from your solution.

You can use being stuck as an opportunity to make significant improvements in your logical reasoning skills.

When others post their good questions, give them feedback on how good they are, along with any constructive feedback on how they might improve. And if you can, answer their question!

Don't forget CYF's Asking Good Questions Guide

Maximum time in hours

1

Submission & Review
  • Take a screenshot of the question you posted on Slack and add it to a comment on this issue.
  • Respond to others’ questions with a thumbs up for “Well written question” and add comments on what you liked about the question and any suggestions for how the question can be further improved. Take a screenshot of your reaction or feedback and add it to a comment on this issue.
  • You can also answer other people’s questions if you know the answer!
Dominant language
JavaScript
Stars
0
Forks
397
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeYourFuture/Module-Structuring-and-Testing-Data

All issues in CodeYourFuture/Module-Structuring-and-Testing-Data

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.