Zach Holman discusses the various stumbling blocks GitHub encountered as the company grew over the years.
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.
Robert Annett explores some of the issues of upgrading, maintaining or replacing legacy Java and .NET applications that haven't been touched in a decade, providing advice on solving common problems.
Justin Beckwith introduces several ways to deploy ASP.NET, Node, and PHP applications to Windows Azure, including git deployment, TFS deployment, continuous integration and custom scripts.
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.
Ian Goodsell discusses the challenges encountered with tool versioning and new approaches needed to support continuous delivery.
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.
Sandro Mancuso runs a hands-on demo adding tests to a Java legacy code then refactoring it.
John Davies walks through a reference implementation of a in-memory database meant to combine dozens of different legacy databases developed by banks over time.
Ignaz Wanders discusses service versioning, compatibility issues, and how to implement the governing process of service versioning.
Robert Reppel discusses applying DDD and SOLID techniques in order to improve legacy code, exemplifying with real code.
Håkan Råberg and Jon Pither on introducing Clojure to an investment bank team having a large Java code, dealing with cultural differences, the lessons learned, and ways of dealing with legacy code.