This book does not tell you how to write code faster, or how to write code with fewer memory leaks, or even how to debug the code at all. What it does tell you is how to build your product with a better way, how to track the code you write, and how to track bugs in your code. Each chapter considers a different tool - a tool for tracking versions of files, build tools, testing tools, bug-tracking tool, a tool for creating documentation, and tools for creating packaged releases. specific examples of each type of equipment described in sufficient detail so that you can decide which one you want to investigate further. Developers want to write code, not maintain makefiles. Whether as a full-time position or just because they are helpful, all projects have been toolsmiths: making choices about tools, installing them, and then maintaining the tools that depend on others.