4 ms·
I have experienced this same issue many times. But from my experience, I cannot simply pinpoint it to young developers or their education. I have seen this beha
by tompazourek 5y ago
I have experienced this same issue many times. But from my experience, I cannot simply pinpoint it to young developers or their education. I have seen this behavior with several older people, university educated, with many years of professional experience. So not just an age/generational thing, in my opinion.
Maybe they have seen so many red herrings that they don't even trust that the error message could contain something useful and relevant? Or maybe they just learned to skim through everything, and don't actually read stuff.
- vladvasiliu 5y agoI have the same experience. I also don't understand why, when they ask for help, they can never be bothered to say what they're trying to do, what error message they got, etc. It feels like they're doing me a favor when I try to help them fix something.
- waylandsmithers 5y agoRight. When I was learning to code a more seasoned dev told me "The code doesn't do what you want it to do, only what you _tell_ it to do." Really helped me gain the mindset that not only was it my mistake that resulted in code not running, but that it was fixable. Like a game of ping pong. You hit the ball, sometimes the compiler hits it back.
- politician 5y agoThen there’s the StackOverflow effect: where you ask a reasonable question X and get a bunch of upvoted condemnations along with directions to do Y instead.
- loopz 5y agoOr, why would you ever consider doing X at all? Ok, thanks for being unhelpful.
- cbushko 5y agoI think it comes down to passion and curiosity. Those are two things can happen at any age and education. It is also something that ebs and flows based on energy levels.
- Noujin 5y agoI think the same. It's so typical everyone here tries to pin characteristics to exact professional groups. The amount of anecdotal evidence here is too damn high.