So there are two things that it comes down to for me.
First, the interview is where your skills are measured. The resume and all those things provide a strong indication that you'd be a good fit. No amount of portfolio or github replaces that, so thats why they're still secondary materials.
Second, for folks starting off with no previous dev experience, unless they've never worked anywhere they actually DO have experience, just not paid development experience. So their resumes and everything emphasize how they still can deliver results regardless of their environment, and their technical skills is yet another way they can do that.
Its that last sentence that makes the difference. If we reduce ourselves to a collection of technical skills we actually don't have value for companies and teams. The magic is connecting our effort to results.
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.
So there are two things that it comes down to for me.
First, the interview is where your skills are measured. The resume and all those things provide a strong indication that you'd be a good fit. No amount of portfolio or github replaces that, so thats why they're still secondary materials.
Second, for folks starting off with no previous dev experience, unless they've never worked anywhere they actually DO have experience, just not paid development experience. So their resumes and everything emphasize how they still can deliver results regardless of their environment, and their technical skills is yet another way they can do that.
Its that last sentence that makes the difference. If we reduce ourselves to a collection of technical skills we actually don't have value for companies and teams. The magic is connecting our effort to results.