<Getting Hired: What You Can Do To Prepare>: <More actionable ways to Get Good >

[CBID2]

Describe your suggestion

The "Get Good" subsection provides great tips, but I think it would be beneficial to mention more specific ways learners can improve and learn their skills. I've recently read some articles written by people who landed jobs as a result of participating in the 100 Days of Code challenge and contributing to open source projects, and I believe this can be a great way to emphasize the importance of getting good.

Update

Through other people’s suggestions, I will add the open source suggestion to the Portfolio section and raise a related issue about adding information on 100 Days of Code to the beginning section

Path

Foundations

Lesson Url

https://www.theodinproject.com/lessons/node-path-getting-hired-what-you-can-do-to-prepare

Checks

• [X] I have thoroughly read and understand The Odin Project Contributing Guide
• [X] Would you like to work on this issue?

(Optional) Discord Name

Chrissy

(Optional) Additional Comments

No response

[CouchofTomato]

I wouldn't mind an additional section mentioning learners should keep going with their own projects and challenges perhaps. Happy to hear others opinions on this.

[rlmoser99]

I'm not sure how 100 days of code will be helpful in this lesson. Isn't that the idea to just code anything for 100 days straight? I believe people already have done that by doing our curriculum. If I am mistaken, can you clarify what 100 days of code is and how it can be helpful to someone that is starting the job hunting process.

Contributing to Open Source is a great thing to add to this lesson. I would add it as it's own section above "Build a Portfolio", because it is partly to help build your portfolio, but also to continue growing.

[CBID2]

I'm not sure how 100 days of code will be helpful in this lesson. Isn't that the idea to just code anything for 100 days straight? I believe people already have done that by doing our curriculum. If I am mistaken, can you clarify what 100 days of code is and how it can be helpful to someone that is starting the job hunting process.

Contributing to Open Source is a great thing to add to this lesson. I would add it as it's own section above "Build a Portfolio", because it is partly to help build your portfolio, but also to continue growing.

Hi @rlmoser99. From what I've seen, 100 days of code is a challenge where people either learn how they code or focus on improving their skills in a specific language for 100 days and they document their progress. To recruiters, this signals that the candidate is eager to learn new skills and takes accountability for it. Since the challenge encourages people to document their experience, recruiters can see how the participants implement their new knowledge, which can increase their qualifications for a role. Does that clarify things?

[Eveieve]

Hi, this is my first time leaving a comment on the open issue, please let me know if isn't encouraged for contributors other than the author/maintainers to leave a comment on open issues.

I did 100 days of code challenge myself on Twitter because I thought it'd be a good way to discipline myself at the very beginning of TOP. And most of its participants are complete beginners who are motivating one another by tagging #100daysOfCode in their posts. Occasionally there were people still doing the challenge even after their initial 100 days, resetting the day to 0 and starting all over again. But I can say that that is rare.

Having said that, including a suggestion on 100 days of code challenge is in my opinion a bit out of place, since the Getting Hired Section is the very last course of the entire curriculum. Learners are expected to have coded for over 100 days already.

If we were to include a suggestion on 100 days of code challenge, I think it'd be a good fit at the beginning of the curriculum - in the foundations course - instead of in the Getting Hired course. And I do think it's a reasonable suggestion, for those who want some more social support and accountability at the start of their programming journey.

[CouchofTomato]

Thanks for your contribution @Eveieve

We welcome input from everyone.

[CBID2]

Hi, this is my first time leaving a comment on the open issue, please let me know if isn't encouraged for contributors other than the author/maintainers to leave a comment on open issues.

I did 100 days of code challenge myself on Twitter because I thought it'd be a good way to discipline myself at the very beginning of TOP. And most of its participants are complete beginners who are motivating one another by tagging #100daysOfCode in their posts. Occasionally there were people still doing the challenge even after their initial 100 days, resetting the day to 0 and starting all over again. But I can say that that is rare.

Having said that, including a suggestion on 100 days of code challenge is in my opinion a bit out of place, since the Getting Hired Section is the very last course of the entire curriculum. Learners are expected to have coded for over 100 days already.

If we were to include a suggestion on 100 days of code challenge, I think it'd be a good fit at the beginning of the curriculum - in the foundations course - instead of in the Getting Hired course. And I do think it's a reasonable suggestion, for those who want some more social support and accountability at the start of their programming journey.

Good point @Eveieve! :) Now that I think about it, putting a suggestion for 100 days does seem more fitting at the beginning, so that they could track their progress when they first start the program.

[CBID2]

Hey @CouchofTomato! :) Can I be assigned to this issue and make a PR for it? I've agreed with the suggestions being made here and want to move forward :)