3 ms·
I'll get stressed out in these types of situations when I'm not accepting things as they are and expecting things to go perfectly like in my mind. If I've work
by mattm 10y ago
I'll get stressed out in these types of situations when I'm not accepting things as they are and expecting things to go perfectly like in my mind. If I've worked on a large issue and been thorough with my testing, I'll commit it and send it to code review. While doing that, thoughts will go through my mind thinking that everything is done and how well I did it. Situations like these are when I'll feel stressed about a poor code review because my expectations don't match reality.
I played hockey with a guy who would just shut down whenever the play didn't go how he thought it should go. If someone didn't pass to him when he thought they should, he would just basically stop and give up as a result of the difference between his expectations and reality.
The key to getting over it is to not dwell on the work you've done in the past and just accept what is being given to you now.
If the code review comes back with bugs and you're getting stressed about it, you're probably still thinking about all the work you did in order to get to the point of committing it. Focusing on the feedback that came back from the code review and how you can implement it will help to get over the anxiety.
I'm writing a book - Programming Spiritually - that helps developers deal with stresses and issues in their work in a more holistic way. If you're interested in being notified on progress with the book you can check out https://leanpub.com/programming-spiritually https://leanpub.com/programming-spiritually