I just wish there were more participants with real corporate coding experience here that could answer some of the career oriented questions.
They are here. They’ve answered some of those questions. I linked you to a great resource. There are answers in many, many past posts.
Seems like most here are people from other walks of life trying to become coders and are guessing at answers.
I would call it researched and learned from others.
Please tell me more specifically what is the ‘wrong question’ and ‘flawed assumption’.
The question implied by, “Wondering how much of a portfolio a person would need to snag a job.”
The question assumes that there is a lower limit somehow, like “What’s the cheapest I could by a new Tesla for if I got the base model and no extras?”
There is no baseline portfolio level of portfolio. As I tried to explain, it is a sliding scale. On the low end it “no” portfolio, which can get you a job but the odds are slim and the pay won’t be good. On the other end is an amazing portfolio showing years of experience in multiple languages/frameworks/libraries and technologies. That portfolio is still not certain of a job but has a much, much greater probability and for much better pay.
I have coded in html, php and css but have no exp in node, ruby, these newer languages.
I think the flawed assumption is that your energy should be in sprucing up a weak (no offence, I’m just going off the little you’ve shared) portfolio. It’s like asking, “I have a really weak resume - what suit should I wear to the interview to hide that?” Instead, I would suggest building the resume/portfolio.
Don’t take my word for it. Start doing job searches. If you can find a job that will accept what you’re offering, then jump on it. You must be looking at very different job postings than I am.
With “html, php and css”, you have a lot of competition. There are guys with a list ten times as long trying to find work. And the age where “html, php and css” was enough to get a web dev job is long gone. Most people can do that themselves. Or if they need something that simple, they can easily build something on Wordpress. With “html, php and css” you might get a few freelance jobs from people that don’t know better, but that won’t be much.
These threads are always tedious. I don’t want to focus it in on you, but these tend to come across as, “I’m insecure about my experience, but I want to find people that will tell me it’s enough to get a job and I’m not going to like answers that tell me otherwise and I’m going to keep asking until I get the answer I want.”
But maybe you’re right. Maybe there is some magical, hidden treasure trove of great jobs out there for people with a minimal level of skills that have been made practically obsolete by automatic web page generators. Maybe they open up to you if you have the perfectly formatted portfolio.
I’m giving the standard advice from these threads in the past, is to build your portfolio. FCC’s coursework will leave you with a couple dozen projects and an experience with many libraries and technologies. That seems like a better idea than worrying about how to make your portfolio seem better - make it better.
Let us know if you find a job. I’ve got to get back to finishing up the backend section. You call it “spinning wheels” - I call it working with Node, servers, http requests, Express, Mongo, Mongoose, Passport, Flash, Sessions, the Yelp API, Bootstrap, JQuery, Handlebars. The technologies I’ve gotten to work with over the course of this program are too many to list. This strategy works better for me.
If you want, put together a portfolio site and post it for people to see. People have done that in the past. It will get you much better feedback. Vague questions don’t seem to get much traction here.
But I’ve said all I want to say. Have a good life.