Immersion theory. At this stage, a lot of what you don't know are "unknown unknowns". So outside (or in between) your other commitments, try and always be looking at or reading about code, as this will help the unknowns surface faster and help your brain with pattern recognition of common practices and syntax for your language/framework/etc.
Applying for jobs: This is the one point, with all due respect, I disagree with. I've also been told it's good to apply for jobs early, which I agree with, but imo, 2 months is far too early.
The amount of time spent applying and dealing with rejections would be better spent coding. And even if you got a job somewhere, it probably won't end well. Being a developer is already stressful enough, so imagine how much pressure you'd feel if you started a dev job not even being familiar/comfortable with the role you were hired for. It could end badly which would hinder your future motivation
Take that with a grain of salt, love what you're doing otherwise :)
Hey Jordan, Your comment gave me a different insight to how I currently look at things so thank you. I have always read these type of tweets on twitter "15 years as a developer and I still don't know what I am doing" from experienced developers and that made me think, may be I can have a job too where I don't know what I am doing but can learn through the process of a full-time/part-time/internship. Being a developer is definitely stressful enough but shouldn't we get out of our comfort zone earlier rather than later or at least try?
2 months is definitely way too short to apply to any jobs I totally agree. But there are people out there who has a full-time job not even relating to programming. Wouldn't it be better to get a job early even if you are uncomfortable so that you don't have to separately manage time to learn programming?
And also no one would hire me with 2 months of experience even I know that but by the time I do I will possibly have 8-12 months of experience and I already know the process of applying. I know earlier on what set of skills companies want, what I can improve as a developer from now on, what particular things I need to focus on other than coding to do better in an organisation and so on. That is the scenario I actually visualised in my head.
All this aside, freelancing might be the most easiest route to start with as a new developer.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Good work. Here's my 2 cents:
Take that with a grain of salt, love what you're doing otherwise :)
Hey Jordan, Your comment gave me a different insight to how I currently look at things so thank you. I have always read these type of tweets on twitter "15 years as a developer and I still don't know what I am doing" from experienced developers and that made me think, may be I can have a job too where I don't know what I am doing but can learn through the process of a full-time/part-time/internship. Being a developer is definitely stressful enough but shouldn't we get out of our comfort zone earlier rather than later or at least try?
2 months is definitely way too short to apply to any jobs I totally agree. But there are people out there who has a full-time job not even relating to programming. Wouldn't it be better to get a job early even if you are uncomfortable so that you don't have to separately manage time to learn programming?
And also no one would hire me with 2 months of experience even I know that but by the time I do I will possibly have 8-12 months of experience and I already know the process of applying. I know earlier on what set of skills companies want, what I can improve as a developer from now on, what particular things I need to focus on other than coding to do better in an organisation and so on. That is the scenario I actually visualised in my head.
All this aside, freelancing might be the most easiest route to start with as a new developer.