Review your Development Plan
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 75/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- documentation
Research direction
Read the Learning Objectives and SMART-goal examples in the issue. Review your Career Development plan, identify the SMART-goal format, and revise one short-, medium-, and long-term goal. No submission is required; feedback can be requested from a mentor or peer.
Written by the indexing model from the issue text.
Description
Learning Objectives
- Review your development plan
- Identify the format of a SMART goal
- Revise one short, medium, and long term SMART goal in your plan
Why are we doing this?
Work on your Career Development plan, so that it reflects your learnings and where you evolved. Your goals might be different now, and writing them down can keep your focus and give you a tool to discuss them with anyone you trust who would like an opinion.
Remember: 2-3 areas are enough to change in such a short time, so it's better to focus on a few, get them nailed, and then choose another area.
Technical knowledge is important, but the skills and processes are also important so you can get a job in tech. So think about both sides.
Examples of goals
- Short term: Practicing coding = Code 1 hour a day on weekdays
- Medium-term: Enhance my written English = Trying to correct by myself the errors that the automated grammar tool is showing in my text
- Long term: Get a job in tech = Send 1 tailored CV per day when I have graduated from Code Your Future
Maximum time in hours
0.5
Submission & Review
Your development plan is your own and so there is no need to submit it for review. If you would like feedback you could share it with a mentor or peer you respect and ask for their advice.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 276
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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-Data-Flows
-
🏕 Priority Mandatory 📅 Sprint 3 Core Module-Data-Flows Submit:None 🦔 Size Tiny
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 2 Core Module-Data-Flows Submit:None
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
🏕 Priority Mandatory 🐂 Size Medium 📅 Sprint 3 Core Module-Data-Flows Submit:None
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
🏕 Priority Mandatory 🐂 Size Medium 📅 Sprint 2 Core Module-Data-Flows Submit:None
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
🏕 Priority Mandatory 🐂 Size Medium 📅 Sprint 1 Core Module-Data-Flows Submit:None
Difficulty 1/5 1-3 hours Newbie friendliness 35/100
All issues in CodeYourFuture/Module-Data-Flows
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
palladius/rails8-app-on-gcp#145 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
dotenvx/dotenv-vscode#139 ·
-
test-change-proposal
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
web-platform-tests/interop#1455 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100