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.
Olve Maudal details machine code generated by snippets of both legal and illegal C code, discussing it in the context of ISO/IEC 9899 standard (the C standard).
Mike Long describes techniques for managing large legacy restoration projects, using a roadmap, prioritizing technical debt remediation tasks and motivating devs and stakeholders during the process.
Dietmar Kuehl discusses creating a C/C++ source code analyzer based on clang.
James Grenning takes a look at embedded programming 30 years ago or more, and how it can be done better now in C.
Brian Marick shares insight into how one can remain a programmer throughout his career.
Bjarne Stroustrup keynotes on what C++ is in general, how C++ 11 makes simple things even simpler, resource management, generic programming, and concurrency.