Asking for feedback
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- content
Research direction
Start with the coursework instructions and the linked Quercus feedback frameworks. Done means completing the peer feedback session, writing the 250-word reflection with one action for each strength and development area, and updating the Development Plan if applicable.
Written by the indexing model from the issue text.
Description
Coursework content
Invite one fellow trainee from the class you have worked with this week for a feedback session. Arrange the call so you can give and receive feedback and get more insight into how you are progressing with your learning.
Read about the different frameworks of feedback on Quercus, so you can think about how you will structure the feedback to be given.
Estimated time in hours
1
What is the purpose of this assignment?
To provide and receive constructive feedback on your and your peers' behaviours in the last class.
How to submit
- Prepare the feedback for your peer. You must have at least 1 positive and 1 to be developed example.
- When you receive the feedback, please remember your active listening techniques.
- Write a 250 words essay reflecting on your strengths and development areas as a result of their feedback and what is one action for each you will take.
Anything else?
Remember to update your Development Plan, if applicable.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 397
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CodeYourFuture/Module-Structuring-and-Testing-Data
-
🏕 Priority Mandatory 📅 Sprint 1 Core Submit:None
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
🏕 Priority Mandatory 📅 Sprint 3 Core Module-Structuring-And-Testing-Data Submit:None 🦔 Size Tiny
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 1 Submit:PR
Difficulty 3/5 1-2 days Newbie friendliness 72/100
-
:gear: bug 📅 Sprint 3 Module-Structuring-And-Testing-Data NotCoursework
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
-
🏕 Priority Mandatory 📅 Sprint 1 Core Module-Structuring-And-Testing-Data Submit:None 🦔 Size Tiny
Difficulty 1/5 Under an hour Newbie friendliness 35/100
All issues in CodeYourFuture/Module-Structuring-and-Testing-Data
Similar issues
-
ai-observability bug team/ai-observability
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AllTheMods/ATM-10-L#19 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
SignalK/n2k-signalk#345 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
JuliaPluto/PlutoPlotly.jl#72 ·