Code Review: How and When - Tulsa TechFest 2016
•0 likes•229 views
Report
Share
Download to read offline
You want to improve your software skills. That's a given. You may be a mentor or a manager who needs to improve the knowledge sharing among your software developers across different projects. Code Reviews can do just that while improving code quality in your projects. Code Review not only builds developer team spirit but also offers new ways to improve a software solution. You'll walk away from this session with in-depth understanding of Code Review to strengthen your team.
More Related Content
What's hot
What's hot(18)
Viewers also liked
Viewers also liked(20)
Similar to Code Review: How and When - Tulsa TechFest 2016
Similar to Code Review: How and When - Tulsa TechFest 2016(20)
More from Paul Gower
More from Paul Gower(11)
Recently uploaded
Recently uploaded(20)
Code Review: How and When - Tulsa TechFest 2016
- 2. Code Review How And When @paulmgower
- 3. I’m Paul Gower. Principal Consultant at Lunamark @paulmgower
- 4. AGENDA What Is Code Review1 2 3 How and When Why Code Review
- 5. What Is Code Review 1
- 6. Father of Code Review http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=5388086&filter%3DAND%28p_IS_Number%3A5388084%29 aka Fagan Inspections
- 7. Fagan Inspections Good for Mission Critical Software
- 12. Email pass-around Please don’t do this!
- 13. Pair Programming
- 23. How and When 2
- 24. How NOT to Code Review
- 27. Reviewer: Focus on the code
- 28. Reviewer: Focus on the code Don’t say: “You didn’t name these variables well!”
- 29. 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?”
- 31. Reviewer: Find a positive point
- 34. Tips and Tricks
- 35. Less Than 200 Lines Of Code
- 37. Less Than 60 Minutes
- 38. Less Than 60 Minutes http://www.news.illinois.edu/news/11/0208focus_AlejandroLleras.html
- 40. Daily Code Review http://blog.fogcreek.com/effective-code-reviews-9-tips-from-a-converted-skeptic/
- 41. Always Use A Checklist
- 42. Always Use A Checklist http://www.codeproject.com/Articles/593751/Code-Review-Checklist-and-Guidelines-for-Csharp-De
- 43. Don’t Review What Can Be Automated
- 44. Static Code Analysis Tools
- 45. Static Code Analysis Tools
- 46. Static Code Analysis Tools
- 47. Static Code Analysis Tools
- 48. Static Code Analysis Tools
- 49. Static Code Analysis Tools
- 51. “ “…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
- 53. Before After 2% 55% Code Review Case Studies
- 56. Reasons to Code Review
- 58. Save Money
- 59. Easier To Find Other’s Mistakes
- 63. “ “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
- 64. 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