Exactly that's why I'm spending a whole day fixing "small" bug. I believe you faced this: you make a small fix, but then SOMEHOW GOD WHY this touches a place in a project not even related. And then you found deeper and more general mistake, try to fix it, and again it pulls another issue, a snowball is growing and finally hits your face.
What's the result: the customer gets a shitty product, you are frustrated. All this because someone decided he/she could be a software developer.
You did really good job in this post - described how to be motivated and become a better programmer. But we are not living in a perfect world, full of unicorns. That is why I prefer to give practical advice, that everyone could try right now.
I agree I've been in a similar situation. More often than not, I've caused this situation to arise. But there's a big difference between telling someone "They shouldn't be in this profession" v/s "Here's how you can do better in this profession".
We aren't living in a world of unicorns and we should find better ways to imparting this knowledge. Everyone stumbles when they learn to walk. Imagine if your parent told you that you weren't cut out to walk instead of helping you improve your gait and make your legs stronger.
It's already too late to tell someone who's messing with a real project "You shouldn't be in this profession". I wish, but I'm realist. That's why I've added number to my advice - #0 (see my first comment, I have no idea why it starts with "1.", in the editor I see "0.". Some bug, probably.). I just want to prevent appearing of new "stackoverflow-developers".
And if we are playing in crazy comparisons, imagine the doctor, that keep failing in diagnosis, but keeps trying because keep hearing, how he/she can become better in his profession.
Exactly that's why I'm spending a whole day fixing "small" bug. I believe you faced this: you make a small fix, but then SOMEHOW GOD WHY this touches a place in a project not even related. And then you found deeper and more general mistake, try to fix it, and again it pulls another issue, a snowball is growing and finally hits your face.
What's the result: the customer gets a shitty product, you are frustrated. All this because someone decided he/she could be a software developer.
You did really good job in this post - described how to be motivated and become a better programmer. But we are not living in a perfect world, full of unicorns. That is why I prefer to give practical advice, that everyone could try right now.
I agree I've been in a similar situation. More often than not, I've caused this situation to arise. But there's a big difference between telling someone "They shouldn't be in this profession" v/s "Here's how you can do better in this profession".
We aren't living in a world of unicorns and we should find better ways to imparting this knowledge. Everyone stumbles when they learn to walk. Imagine if your parent told you that you weren't cut out to walk instead of helping you improve your gait and make your legs stronger.
It's already too late to tell someone who's messing with a real project "You shouldn't be in this profession". I wish, but I'm realist. That's why I've added number to my advice - #0 (see my first comment, I have no idea why it starts with "1.", in the editor I see "0.". Some bug, probably.). I just want to prevent appearing of new "stackoverflow-developers".
And if we are playing in crazy comparisons, imagine the doctor, that keep failing in diagnosis, but keeps trying because keep hearing, how he/she can become better in his profession.
That's literally how Med School works. :)
School - maybe, but not a hospital. Such a doctor would be fired in a blick.