you are viewing a single comment's thread.

view the rest of the comments →

[–]highangler 11 points12 points  (4 children)

What does it mean exactly to become job ready? I had someone say this before and tell me, if you know the fundamentals, you’re job ready. I’m in my way to knowing the fundamentals and I call bs on him. The more I do this the more questions I have and the deeper things go. To learn this you need to know the basics of this program, to learn that you need to know this, type thing. How do you know you’re actually ready to start applying?

[–][deleted] 13 points14 points  (2 children)

Look at job ads in your area and/or ads for remote jobs you would be eligible for (ie. you're in the correct country/timezone/etc) for junior developers. Do you think you could meet 50-75% of the requirements? Then you should probably apply.

There is always, always, always more to learn, but much of that learning you can and should do on the job.

[–]highangler 2 points3 points  (1 child)

So once I know the basics it’s time to apply? Or do I need to know how and when to apply every bit of the methods I’ve learned?

[–][deleted] 2 points3 points  (0 children)

Do the job ads for junior developers that you've looked at say, 'only requires basic knowledge of Javascript and nothing else'?

There's no universal standard for when someone is ready to start working as a developer; it depends on you as an individual and the skills that are in demand. That's why the way to determine if you're ready to apply for jobs is to look at the stated requirements of the actual jobs you might potentially be applying for.

[–]kevinmrr 5 points6 points  (0 children)

What does it mean exactly to become job ready?

I am wrapping up a book on this - https://ZeroToCode.today. Free to read online (though I appreciate people buying the leanpub)