Avoid the Zone of Chaos: Economics of Quality and Productivity via Code Review
Details
It's called the Zone of Chaos for a reason. When piles and piles of defects and untested code reach the testers or, shamefully, your users: all hell breaks loose in your organization
Why? Because:
IT IS 2400% TIMES MORE EXPENSIVE TO FIX BUGS IN PRODUCTION THAN IN DEVELOPMENT
So, what can your team do to ensure both productivity and quality to avoid the zone of chaos?
Here's one thought: Capers Jones has researched inspection / code review and determined that good code review reduces defects more than does testing. Here are two pretty pictures to hang in your office. If you're lucky, your manager will give you a gold-plated frame for them. Not because you're guilty of "gold-plating", but because you're SAVING MONEY.
http://blog.smartbear.com/post/12-03-14/better-code-starts-with-review/
http://photos1.meetupstatic.com/photos/event/5/f/7/0/event_128364432.jpeg
http://photos4.meetupstatic.com/photos/event/4/2/d/8/event_128357112.jpeg
Meetup Agenda:
7:30 - 8:30: Dinner and drinks, free developer discussion
8:30 - 8:35: Announcements and Pluralsight 30-day free training giveaway (Read the two articles linked below to qualify!)
8:35 - 9:35: Focused discussion on The Economics of Quality and Productivity with Code Review -- featuring a demo of VS Code Quality Analysis
9:30+: Open discussion
More Questions:
-
How does your team define productivity and quality??
-
When your team faces schedule pressure, how does it react?
-
What are your own hard earned lessons related to this subject?
-
Does the invisible nature of code that's underneath the UI layer make it far too easy to allow brittle, unstable code to persist in your code base right up until the end of a sprint or even after deployment?
These are just a few of the questions that we must constantly concern ourselves with in our profession.
And, there are many, many practices and tools that we can employ to combat this problem:
-
Frequent demos and feedback (agile processes)
-
Coding standards and code review, pair programming
-
IDE tools: Resharper, etc
-
Static code analysis tools and code coverage tools
-
Practice refactoring
-
Any or all of the *-Driven-Developments (TDD, BDD, ATDD, DDD, etc)
-
Defect Prevention versus defect discovery by the QA team
Required Reading:
Software Quality at Top Speed, Steve McConnell: http://www.stevemcconnell.com/articles/art04.htm
Do You Inspect?, Capers Jones:
http://www.drdobbs.com/architecture-and-design/231903203
Better Software Starts with Code Review:
http://blog.smartbear.com/post/12-03-14/better-code-starts-with-review/
Additional Resources:
11 Best Practices for Peer Code Review:
http://support.smartbear.com/resources/cc/11_Best_Practices_for_Peer_Code_Review.pdf
Code Review: http://en.wikipedia.org/wiki/Code_review
Long running thread on original Wiki:
http://c2.com/cgi/wiki?HowFastCanYouWriteCode
Refactoring: http://en.wikipedia.org/wiki/Code_refactoring
VS Code Analysis:
http://msdn.microsoft.com/en-us/library/3z0aeatx.aspx
Resharper, JustCode:
