Learn from rejections
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
Research direction
Start with the Coursework content in this issue and reflect on a personal experience of rejection. Write a 250-word response addressing what you learned, what it taught you about yourself, positive outcomes, and advice for others. Share the Google Doc link on the ticket and provide mentor access when requested.
Written by the indexing model from the issue text.
Description
Learning Objectives
- Reflect on previous experiences
- Identify key learning points from that experience
Coursework content
Everyone experiences rejection. Learning from past examples helps us to deal with the possible future instances. Think of some situations where you felt rejected. Perhaps you didn’t get on a sports team or didn’t get offered a job. Write a 250-word text about this personal experience. Try to answer the following questions:
- What did you learn as a result of this rejection?
- Did the experience teach you more about yourself?
- What positive things came out of the rejection (perhaps not immediately, but later)?
- How would you recommend other people to behave in that situation?
Maximum time in hours
1
Submission & Review
Share the link to the Google doc of your reflections on your ticket. You don't have to publish your personal document on the public internet, but do give access to a mentor when they ask to review.
- 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 ·