Dan North believes Agile scales if teams achieve contextual consistency through shared guiding principles, a clear vision and a common understanding.
Wojciech Seliga shares from experience how complex it can be to deal with thousands of tests -unit, functional, integration, performance- for Atlassian JIRA and what they did to bring it under control
Roger Orr solves a problem with different levels of complexity trying to answer what the complexity notation actually means and why it is important in practice.
Bjarne Stroustrup discusses features that might appear in C++14: braces for copy initialization, return type deduction in functions, generic (polymorphic) lambdas, user-defined literals, etc.
Alan Griffiths shares the organizational process, the technological challenges and the solutions adopted by a team developing a C++ systems component.
Tobias Darm discusses how some of the GoF patterns can be implemented differently in C++11 using Boost libraries.
Charles Bailey takes a look at Git Index’s internals, explaining why it is used, what and how is stored in it, and what operations can be used against it.
Zsolt Fabok presents several methods that can be used to find areas which are worth testing so that organizations do not have to spend more effort on testing than what is absolutely necessary.
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.
Chris Oldwood discusses what it takes to create robust software: correct error detection and recovery, testing systemic effects, app monitoring and configuration.
Peter Pilgrim introduces Scala to advancing beginners: getting the most out of Scala, working with popular Java frameworks, the build tools and some of the new features of Scala 2.10.
Johan Herland explains how Git does branching and merging in a distributed (and partially disconnected) environment, how to rewrite a commit history, and why staging is useful.