There's a lot of people stuff too. I have found that junior developers, perversely, are more defensive about bad decisions than senior folks. They tend to be quicker to leap to conclusions or become attached to a particular technical approach to a problem. Of course, senior people make these mistakes too, but, I find, at a lower rate.
It's not universal. I have no doubt that there are kids with six months of experience who perform better than me after my six years. But, I'd also be willing to bet that's an exception, not the rule.
Very true, I think the defensive part comes from feeling comfortable with a limited toolkit. It's only natural to try push what you feel comfortable with, my experience is a lot of the more junior staff I work with are more pushy and emotional with their tech interests, however often relax and become more approachable if you provide guidance and help them learn something new in a comfortable environment.
Also, you've been through the process of writing things that later turned out to be hard to maintain/scale poorly/bad_attribute_x later on even when you thought it was good to start with. The more I work, the less surprised I am that my solution isn't the best one or that there was a situation/edge case I hadn't thought of.
Comments
There's a lot of people stuff too. I have found that junior developers, perversely, are more defensive about bad decisions than senior folks. They tend to be quicker to leap to conclusions or become attached to a particular technical approach to a problem. Of course, senior people make these mistakes too, but, I find, at a lower rate.
It's not universal. I have no doubt that there are kids with six months of experience who perform better than me after my six years. But, I'd also be willing to bet that's an exception, not the rule.
Very true, I think the defensive part comes from feeling comfortable with a limited toolkit. It's only natural to try push what you feel comfortable with, my experience is a lot of the more junior staff I work with are more pushy and emotional with their tech interests, however often relax and become more approachable if you provide guidance and help them learn something new in a comfortable environment.
I think for senior people the notion of "you are not your code" tends to sink in after a few rewrites/refactorings or total technology replacements.
Also, you've been through the process of writing things that later turned out to be hard to maintain/scale poorly/bad_attribute_x later on even when you thought it was good to start with. The more I work, the less surprised I am that my solution isn't the best one or that there was a situation/edge case I hadn't thought of.