Austin Bingham answers questions on reviews: how long should they be, what should be reviewed, how do reviews account for an increase in quality and ROI?
Olivier Gourment explains, step by step, how any team or organization can adopt Agile code reviews which are known to reduce the costs of defect fixing by half.
Arjan van Leeuwen overviews code reviews advantages and disadvantages, how much can be done in a code review, types of critiques, how to handle critiques and conflicts that might arise from them.
Ryan Slobojan discusses how to perform issue tracking, code review, commits and builds in an automated manner by integrating Git, Gerrit, Hudson and Mylyn.
Mike Rozlog discusses the need for software audits, proposing five code reviews that every developer should use: Numerical Literal, String Literal, god Method, Shotgun Surgery and Duplicate Code.
Gerard Holzmann discusses Spin, a design analyzer tool, and Scrub, a code review tool, used by Jet Propulsion Laboratory to analyze and fix the software used for solar system exploration missions.
Magnus Robertsson shows how to control the code architecture to avoid an architectural drift leading to a big-ball-of-mud: peer review, code analysis, and zero tolerance to warnings and errors.
In this talk from RubyFringe, Luke Francl asks: is developer-driven testing really the best way to find software defects? Or is the emphasis on testing and test coverage barking up the wrong tree?
Creating secure code requires more than just good intentions. Static source code analysis can be used to uncover the kinds of errors that lead directly to vulnerabilities. Brian Chess shows you how.