All of what you said in your reply is along the lines of what I had hoped for, but I have run into too many in our field who legitimately believe that one must go through a rite of passage, and earn knowledge through painful acquisition.
The question about the interview came to be because I am still a little raw from an internal interview I did quite recently where the interviewer was more interested in showcasing his expert knowledge and denigrating my own skill set than he was about determining whether I would be the candidate that was the best fit for the position. Since this chucklehead was the guy I would have to be working closely with if I got the job, I went and spoke with my manager after the interview and personally passed on the position. I don't know if I ultimately passed or failed his interview, but he certainly failed mine.
All in all, I really didn't mean to focus on C, because the main area where this is hitting our industry is in web development. The bootcamps are of quite checkered quality, and it is hard to know if someone is a well-rounded developer capable of working in multiple frameworks as well as in plain vanilla JS when needed, or if your newest hire is only as skilled as the framework they were taught in, and resembles a fish out of water when the project requirements are switched suddenly. Someday, our field might become more formalized in our evaluation of an engineer's skill set, just like the mechanical, electrical, or civic engineers are. Students will sit for a PE certification upon graduation from whatever program they study. Someday.
Once again, I do not see it as neither a rite of passage, nor a painful way to learn.
I'm just saying that I don't see it as a bad advice because I would recommend people to do so!
That is what I chose to do back then and it worked for me. And for a curious person, it can be quite fun actually to understand what the IDE is doing when you click the build and run button.
But it is only a friendly advice. I won't judge a person who choose not to follow it 😉!
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.
All of what you said in your reply is along the lines of what I had hoped for, but I have run into too many in our field who legitimately believe that one must go through a rite of passage, and earn knowledge through painful acquisition.
The question about the interview came to be because I am still a little raw from an internal interview I did quite recently where the interviewer was more interested in showcasing his expert knowledge and denigrating my own skill set than he was about determining whether I would be the candidate that was the best fit for the position. Since this chucklehead was the guy I would have to be working closely with if I got the job, I went and spoke with my manager after the interview and personally passed on the position. I don't know if I ultimately passed or failed his interview, but he certainly failed mine.
All in all, I really didn't mean to focus on C, because the main area where this is hitting our industry is in web development. The bootcamps are of quite checkered quality, and it is hard to know if someone is a well-rounded developer capable of working in multiple frameworks as well as in plain vanilla JS when needed, or if your newest hire is only as skilled as the framework they were taught in, and resembles a fish out of water when the project requirements are switched suddenly. Someday, our field might become more formalized in our evaluation of an engineer's skill set, just like the mechanical, electrical, or civic engineers are. Students will sit for a PE certification upon graduation from whatever program they study. Someday.
Once again, I do not see it as neither a rite of passage, nor a painful way to learn.
I'm just saying that I don't see it as a bad advice because I would recommend people to do so!
That is what I chose to do back then and it worked for me. And for a curious person, it can be quite fun actually to understand what the IDE is doing when you click the build and run button.
But it is only a friendly advice. I won't judge a person who choose not to follow it 😉!