I'm blaming the same things, so we are all good, I just want him to reconsider his hate approach and move into a more constructive one.
I'm speaking with junior web devs daily, I have studied the same problem in the last 2 years or so, I've seen the gaps they have, I'm not surprise if questions like "how to sum 2 numbers with react" exists on stackoverflow :(.
have the resources needed available online(for the most part) and they should take the time to learn, and it takes time to get good at anything.
As a fresh mentor, I quickly realized that my "main duty" is to filter the resources. I think the today student problem is not the lack of good material, is the abundance of the lower quality material, and when you are studying you don't know the difference, you learn the "highest rated" personality or course.
After a few months of production, the "damage" is done, you cannot say "you learned the wrong way" because the answer is "but how? I can build websites, I solve problems". The best way to "fix the gaps" I have found is to get into the trenches, when they are stuck and explain them how and why they got it wrong.
Instead of "learn Big O and optimization techniques" we can say:
"Your view component is slow because: you see these 4 nested fors? ok, let's draw them on the table and calculate how many times these operations are computed. Now how can we improve them? ...."
Another good way is by example, I found that just by sharing my screen, they learn a lot, like how to use their tools (IDE, dev tools), how to approach a problem and so on.
Good on ya for fixing this from within the trenches! I try to do the same, I have a basics course in PHP set up (in my native language) and we start from the nitty gritty.
People struggle with looping through arrays in their first months, so no wonder they can't really grasp what a framework does. But they definitely need to be brought back to basics.
I've hired juniors, and I had better luck with those that knew "just" html/css/js/php, than with those that "knew" "Laravel/jQuery/Bootstrap", because with the former we had a base to work off of. With the latter they weren't able to navigate simple OOP relationships, let alone debug the first Exception their favorite framework throws up.
The industry is a bad place. We need thousands of develpers today, so we try to rush people through this. But that doesn't work. What you describe is the way to go. But I do agree with the original post as well. And I think it's more about the ones with about a years worth of experience that need to hear those harsh words, just so they're not complacent.
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.
I'm blaming the same things, so we are all good, I just want him to reconsider his hate approach and move into a more constructive one.
I'm speaking with junior web devs daily, I have studied the same problem in the last 2 years or so, I've seen the gaps they have, I'm not surprise if questions like "how to sum 2 numbers with react" exists on stackoverflow :(.
As a fresh mentor, I quickly realized that my "main duty" is to filter the resources. I think the today student problem is not the lack of good material, is the abundance of the lower quality material, and when you are studying you don't know the difference, you learn the "highest rated" personality or course.
After a few months of production, the "damage" is done, you cannot say "you learned the wrong way" because the answer is "but how? I can build websites, I solve problems". The best way to "fix the gaps" I have found is to get into the trenches, when they are stuck and explain them how and why they got it wrong.
Instead of "learn Big O and optimization techniques" we can say:
"Your view component is slow because: you see these 4 nested fors? ok, let's draw them on the table and calculate how many times these operations are computed. Now how can we improve them? ...."
Another good way is by example, I found that just by sharing my screen, they learn a lot, like how to use their tools (IDE, dev tools), how to approach a problem and so on.
Good on ya for fixing this from within the trenches! I try to do the same, I have a basics course in PHP set up (in my native language) and we start from the nitty gritty.
People struggle with looping through arrays in their first months, so no wonder they can't really grasp what a framework does. But they definitely need to be brought back to basics.
I've hired juniors, and I had better luck with those that knew "just" html/css/js/php, than with those that "knew" "Laravel/jQuery/Bootstrap", because with the former we had a base to work off of. With the latter they weren't able to navigate simple OOP relationships, let alone debug the first Exception their favorite framework throws up.
The industry is a bad place. We need thousands of develpers today, so we try to rush people through this. But that doesn't work. What you describe is the way to go. But I do agree with the original post as well. And I think it's more about the ones with about a years worth of experience that need to hear those harsh words, just so they're not complacent.