>The same as creating art. It is the manifestation of your thoughts and opinions, small and large, put out in to the world.
I respectfully disagree. This thought process is why other people are left holding the bag at 11pm on a Friday fixing the 'art' of someone else. Computer Science is a derivative of mathematics. Math is not art. Math IS beautiful, explicitly because it is NOT ambiguous or subject to interpretation. Math is right or wrong. It works or it is flawed.
Programming isn't art.
edit: forgot a >
I agree that data structures and algorithms are not art, but when combined in unique ways they create art.
I think the problem is the field is so new and these terms aren’t well defined.
Unless you consider anything less than perfect to be wrong, but that’ll just make nobody want to work with you.
You have twisted my words.
I equated it to art as the physical manifestation of something that represents someone's mental imaging / modeling.
I don't see why you think this is the same thing.
Improvement in someone's coding skill is good from a business/colleague/project perspective. And from a "practice paid off" perspective. And positive feedback is always good to give, you certainly shouldn't only give negative feedback.
But you shouldn't get too attached to your code in either case. Today's good code is likely to be tomorrow's bad legacy code anyway. It shouldn't be an "intimate experience," programming for a company is an exercise in utility.
No disagreement. But let's get pedantic:
The umbrella "you are not your code" would dismiss improvement as well. And praise.
Ok, so I am not my code. But if I don't learn from my mistakes my code will not improve.
I... I... I...
Anyway, I much prefer to reframe it this way:
Programming is a very intimate experience.
The same as creating art. It is the manifestation of your thoughts and opinions, small and large, put out in to the world. So sure, don't be offended by critique. But also remember to extend some grace when doing a review.