|
|
|
|
|
by metters
1619 days ago
|
|
This is a good point and a perspective I neglected.
Usually, when receiving feedback on my code I solve this by discussing the _why_ after receiving a _what_ as feedback. When giving feedback, I try to do the same: Instead of just saying what is bad/wrong/smelly etc. and telling how to change the code I’ll also give the reasons why I think so. The discussion afterwards should clarify the remark and I am open to the possibility that I am wrong.
But you are right, at the moment I feel like currently I am giving up my approach/code too easily.
This is partially because my colleagues are quite experienced and I’m very lucky to be able to learn from them. Edit: Improved the punctuation. |
|