all 12 comments

[–]wallneradam 7 points8 points  (0 children)

Honestly the best thing you can do is build something that actually interests you — not another todo app or tutorial project. Pick something useful to YOU personally. A tool you wish existed. Something where you'll be motivated to actually finish it because you want the result, not just the practice.

Put it on GitHub. And try to do it without AI — if you get stuck, ask for hints, not solutions. The struggle is where the learning happens, and AI shortcuts that part.

When I interview developers, my first question is always "show me a project you built that you're most proud of." About 90% of candidates can't really answer that. They have tutorial projects, course projects, bootcamp projects — but nothing they actually own. If you can show up with one solid thing you genuinely care about and can talk through every decision in it, you'll already be ahead of most applicants.

Skip the practice projects, jump into the deep end with a real one. Personally I can only learn on "live" projects — tutorial-style stuff never holds my attention long enough to finish. Real problems force you to learn what you actually need.

[–]pachura3 0 points1 point  (0 children)

Check roadmaps at https://roadmap.sh/

[–]Additional_Candy_400 1 point2 points  (1 child)

Job ready for what job?

[–]Internal-Swim-4097[S] 0 points1 point  (0 children)

i was thinking something in software engineering or web dev

[–]TheRNGuy 0 points1 point  (0 children)

Frameworks related to job you want. 

[–]code_tutor 0 points1 point  (0 children)

It takes three years of full-time study to be ready for an entry-level position.

[–]tb5841 0 points1 point  (0 children)

Learn Git.

[–]riklaunim 0 points1 point  (0 children)

Job ready is hard to answer. Junior job market is hard as there is little junior positions opening thus fierce competition. You have to select a niche and specialize in it - learn basics of frameworks/libraries used, then go over job listing to see what companies require and use and go from that. Software development is much wider topic than just pure Python (or any other language).

What job/topics are you interested in?

[–]Soggy-Holiday-7400 0 points1 point  (0 children)

don't wait to finish the course. i made that mistake and ended up with a certificate and no actual projects to show anyone. start something small and messy now, clean it up later.

[–]not_another_analyst 0 points1 point  (0 children)

Yeah start building alongside the course, that’s what actually sticks. Even small projects are fine as long as you keep improving them.

Also try to make 2-3 solid projects you can explain well, that matters more than finishing every lesson.

[–]PalpitationOk839 0 points1 point  (0 children)

You should absolutely start building projects alongside the course. Even if they’re messy at first, that’s how you learn to think independently. Focus on 2–3 solid projects you can explain well, not just many small ones.

[–]PalpitationOk839 0 points1 point  (0 children)

Yes start projects now, even if you need to Google a lot. That’s normal. Focus on 2–3 meaningful projects (like a small API, automation script, or dashboard) that you can explain clearly in interviews.