Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Review your development plan

Open
#9 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
documentation

Research direction

Start with the Learning Objectives and the examples in this issue, then review your existing Build Your Life plan and first Career Development plan. Done means defining focused short-, medium-, and long-term goals across two or three development areas; sharing with a mentor or peer is optional.

Written by the indexing model from the issue text.

Description

🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 1 Core Module-Structuring-And-Testing-Data Submit:None
Learning Objectives
  • Define short, medium and long-term development goals
Why are we doing this?

Using the Build Your Life plan and your first version of your Career Development plan, we want you to continuously think about the goals you want to achieve: short/medium/long-term. These should be linked to the areas you want to develop. This will help to give you perspective and clarity of where your direction is and if you are doing the right things to get there.

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.

Ensure you are not only thinking of technical knowledge you want to acquire but especially skills and processes that will help you become a developer.

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
397
PR merge metrics
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.