📌 Quality
→ Reviewing code brings standard improvements to your code.
→ Later, it doesn't bring maintenance to your code.
→ Reviewing code brings standard improvements to your code.
→ Later, it doesn't bring maintenance to your code.
📌 Security
→ As your system becomes more complex, we all want to make it so easier to deploy the code & test new features.
→ And sometimes we let security standards slip.
→ As your system becomes more complex, we all want to make it so easier to deploy the code & test new features.
→ And sometimes we let security standards slip.
📌 Reflection
→ Knowing that your code is going to be reviewed, so allow the opportunity to reflect what we've done.
→ We don't want to send the unformatted code to team mates.
→ Knowing that your code is going to be reviewed, so allow the opportunity to reflect what we've done.
→ We don't want to send the unformatted code to team mates.
📌 Personal Development
→ Reviewing code, again and again, updating and deleting it makes an new habit to focus and review it properly.
→ Reviewing code, again and again, updating and deleting it makes an new habit to focus and review it properly.
📌 Teamwork
→ Reviewing your code, enables your team members to share their work and give more users a better understanding of what changes has been to the code.
→ And they might have to use that code for future work.
→ Reviewing your code, enables your team members to share their work and give more users a better understanding of what changes has been to the code.
→ And they might have to use that code for future work.
Thanks for reading this thread ❤️
If you like it , make sure you:
🔷 Like the tweet
🔷 Retweet the first tweet ⚡
For more content , follow:
@MrunayU
If you like it , make sure you:
🔷 Like the tweet
🔷 Retweet the first tweet ⚡
For more content , follow:
@MrunayU
You can read the unrolled version of this thread here: typefully.com
جاري تحميل الاقتراحات...