I’m sure Jessica offers some good analysis, let me offer mine.
Your resume… Keep in mind I can be a harsh critic.
What is this a resume for? When the HR manager is searching their desk and come across this, do you really want to give them a scavenger hunt? You should have a subtitle saying the kind of job you are looking for and probably a few sentences in a “Summary” section that explains further who you are and what type of job you want - straight and to the point.
The Korean and Japanese (I assume) script at the top and the sign language - get rid of them. What does that have to do with your ability as a developer. If you want a “Languages” section at the bottom, include them there. I don’t know if your SO account should be listed under “experience”.
Your non coding job entries are much too long. The ParkJeong entry should be two lines - “English” teacher says all they need to know. The same with the dispatch job.
Your Education entry is too long. It should be three lines. The third line is your majors on the left and your GPA on the right. They don’t care abut your minors or thesis - unless they were directly related to coding, and maybe not even then.
The skills section should be MUCH more prominent. That is one of the most important sections. It should be one of the first things in your resume (for me, after the summary) and have more things in it. I like a list with multiple columns, let it “pop”. We just saved a lot of space with the things we removed above - us it for this.
They don’t care about your interests. It isn’t a dating site. These kinds of things might add color in an interview, but in a resume they just make you seem unfocused and distract the reader. This is where your languages could go. I don’t know if it is that important, but if you must, I would put them here.
Most of my projects are from the fCC curriculum (although the latter ones are particularly polished and personalized, I feel)
Where are they? I would have expected to see your 3 best projects, professional or otherwise.
I agree with ArielLeslie, to a point. Yeah, they aren’t impressive and they are “cookie-cutter”. But if they are the best you have, then use them. But your goal should be to displace them with your own projects, things that you have conceived and built from scratch. Originality isn’t important there, but that you came up with the plan and built it and it is well coded. Having a backend and unit tests would really help, too.
- How much of my productive time should I be focusing on improving my portfolio vs networking/job-hunting?
Does job hunting take that long? When I was learning, I would typically spend 1-8 hours coding (depending on my “real” job) and maybe send up some resumes/applications at the end of the day, maybe 15-30 minutes.
- Should I step away from the fCC curriculum to work on unique projects that will set me apart from other applicants?
Part of the point of the FCC curriculum is to get you ready to make good solo projects. But if you already have those skills, then go for it. I think once you get into the Python stuff, you probably can trail off if you need to - they are related to a different stack. (I wish we had “learning tracks” to make that more clear.)
- Could I perhaps start contributing significantly to some FOSS repositories as a way to both improve my abilities and network? (I ask this because I would much rather be coding than trying to network on LinkedIn.)
If you are ready to do that, then go for it. It is good experience and looks good on the resume.
- Do you agree with the following block-quote?
“I’m not really big on [job] applications. I truly believe one conversation can lead you anywhere … So I’m a big believer in network, network, network.”
I don’t know what he’s talking about. Of the three jobs I’ve gotten, three were gotten through applications. Of the hundreds of jobs I’ve reached out to, I can only think of two job interviews that came from knowing someone who knew someone. I mean, I linkedin is powerful. I think one of my jobs was from a recruiter contacting me on linkedin, but that wasn’t really “networking”, that was me having a presence on the platform, having my skills and resume updated, and a recruiter searching and finding that I matched their requirements.
Take things you read on social media with a grain of salt. Also realize that youtubers make money from views, so they make money from being shocking. If they want attention, they have to say something different than everyone else. There is a real incentive for them to just say crazy stuff.
Sure, go ahead and “network”. I never got a job from it, but I learned a lot from going to local coding meetups and helping out here on the forum. Meet people, talk to people, share ideas, critique each other’s code.