How and When To Code Review
Report
Paul GowerFollow
Jul. 16, 2016•0 likes•354 views
0 likes
Be the first to like this
Show More
views
Total views
0
On Slideshare
0
From embeds
0
Number of embeds
0
Check these out next
How and When To Code Review
Jul. 16, 2016•0 likes•354 views
0 likes
Be the first to like this
Show More
views
Total views
0
On Slideshare
0
From embeds
0
Number of embeds
0
Download to read offline
Report
Software
Are you a software developer who wants to improve your skills? Are you a team lead who enjoys mentoring other developers and improving both their and your coding skills? Or are you a manager who needs to improve the knowledge sharing among your software developers across different projects? Today we will be talking about how Code Reviews can do just this and also improve the code quality of your software projects in the process. Code Review can be a great way to get to know your fellow developers and even learn a different or sometimes better way to build a software solution. At the end of the session you will have a better understanding of the benefits of Code Review as well as some great tips to use in your team today.
Paul GowerFollow
Recommended
DevSecCon Singapore 2018 - Insecurity in information technology by Tanya JancaDevSecCon
PuppetConf 2016: Debugging Diversity – Anjuan Simmons, Assemble SystemsPuppet
Agile TestingAnand Ramdeo
Quality and Testing of AI Algorithms - Enterprise Deep LearningSam Putnam [Deep Learning]
Mobile Keywordsvignes
The complete guide for negative testing | David TzemachDavid Tzemach
How and When To Code Review
- How And When To Code Review Paul Gower @paulmgower
- I’m Paul Gower. Principal Consultant at Lunamark @paulmgower
- AGENDA What Is Code Review1 2 3 How and When Why Code Review
- What Is Code Review 1
- Father of Code Review http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=5388086&filter%3DAND%28p_IS_Number%3A5388084%29 aka Fagan Inspections
- Fagan Inspections Good for Mission Critical Software
- Code Review History
- Over-the-shoulder
- Email pass-around
- Email pass-around Please don’t do this!
- Pair Programming
- Tool-Assisted Code Review
- Tool-Assisted Code Review
- Tool-Assisted Code Review
- Tool-Assisted Code Review
- Tool-Assisted Code Review
- Tool-Assisted Code Review
- Tool-Assisted Code Review
- Tool-Assisted Code Review
- Tool-Assisted Code Review
- How and When 2
- How NOT to Code Review
- Don’t Be This Guy
- Reviewer: Focus on the code
- Reviewer: Focus on the code Don’t say: “You didn’t name these variables well!”
- Reviewer: Focus on the code Don’t say: “You didn’t name these variables well!” Instead: “I don’t understand these variable names, can you help me understand them?”
- Reviewer: Be respectful
- Reviewer: Find a positive point
- Developer: Be humble
- Developer: Prepare Before
- Tips and Tricks
- Less Than 200 Lines Of Code
- Less Than 60 Minutes
- Less Than 60 Minutes http://www.news.illinois.edu/news/11/0208focus_AlejandroLleras.html
- Daily Code Review
- Daily Code Review http://blog.fogcreek.com/effective-code-reviews-9-tips-from-a-converted-skeptic/
- Always Use A Checklist
- Always Use A Checklist http://www.codeproject.com/Articles/593751/Code-Review-Checklist-and-Guidelines-for-Csharp-De
- Don’t Review What Can Be Automated
- Static Code Analysis Tools
- Static Code Analysis Tools
- Static Code Analysis Tools
- Static Code Analysis Tools
- Static Code Analysis Tools
- Static Code Analysis Tools
- 3 Why Code Review
- “ “…the average defect detection rate is only 25 percent for unit testing, 35 percent for function testing, and 45 percent for integration testing. In contrast, the average effectiveness of design and code inspections are 55 and 60 percent.” - Steve McConnell, Code Complete, 2004
- Before After 2% 55% Code Review Case Studies
- Code Review Case Studies Without With 0.82 errors / 100 loc 4.5 errors / 100 loc
- Before Code Reviews
- After Code Reviews
- Reasons to Code Review
- Save Money
- Easier To Find Other’s Mistakes
- Use Peer Pressure To Your Advantage
- Alternative Implementations
- Knowledge Sharing
- “ “The aim is to catch what mistakes you can and to get better – not to attempt perfection.” - Erik Dietrich, “Creating Your Code Review Checklist”, 2015
- Review • No more than 60 mins • No more than 200 lines of code • Use Static Code Analysis • Use Check Lists • Use A Code Review Tool
- THANK YOU! @paulmgower http://bit.ly/cs2016-cr