Read on Twitter
Code reviews are sometimes rough. I was a terrible reviewer early on in my career because I was only looking to improve the codebase _no matter the cost_.
Who knew that when you work on a team, there's a cost to pointing out every tiny detail in a code review.
1/n
Who knew that when you work on a team, there's a cost to pointing out every tiny detail in a code review.
1/n
When you're coding alone, it's easy to feel proud of your code – and you should! – but it's only detrimental when it comes to joining a team.
A code review is, in essence, someone else trying to find flaws in your code to make it more robust.
They're not judging you.
2/n
A code review is, in essence, someone else trying to find flaws in your code to make it more robust.
They're not judging you.
2/n
This is extremely difficult to deal with if either the reviewer or you have low EQ. Angie Jones, a senior dev advocate @ Applitools has a great article on the 10 commandments of code reviews.
https://techbeacon.com/app-dev-testing/10-commandments-navigating-code-reviews?amp&__twitter_impression=true
3/4
https://techbeacon.com/app-dev-testing/10-commandments-navigating-code-reviews?amp&__twitter_impression=true
3/4
If I can leave you with one piece of knowledge it's that you are *not* your code. Writing shitty code != being a shitty developer.
4/4
4/4
