This. The author completely neglected to mention what kind of development he's talking about, but speaking as a reverse engineer - learning how to cope with failure is increasingly important. You're not always going to find a function to hook or a loophole to exploit, and not every customer is going to like the ideas you have or the code that you write. It doesn't matter if you've been programming for 35 years or 3 months... Failure and rejection is part of the business, and being humble enough to accept that, ask the correct questions, and put the work before your ego is just as important as (maybe more important than) your technical ability.
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 guess being good is subjective, people I’ve worked with who I consider great developers are;
I think for me at least it’s more the mindset and less the skill. Most people with x years of experience are good at the programming part.
This. The author completely neglected to mention what kind of development he's talking about, but speaking as a reverse engineer - learning how to cope with failure is increasingly important. You're not always going to find a function to hook or a loophole to exploit, and not every customer is going to like the ideas you have or the code that you write. It doesn't matter if you've been programming for 35 years or 3 months... Failure and rejection is part of the business, and being humble enough to accept that, ask the correct questions, and put the work before your ego is just as important as (maybe more important than) your technical ability.