This book is for developers who want to take her career or skill set and / or project to the next level. If you are a professional software developer with 3 4 years experience looking to bring a higher level of discipline to your project, or learn skills that will help you transition from software engineer to technical lead,? So this book is for you. This book is about practical techniques and practices that will help you and your team achieve that goal. This book is for developers to understand that business software is, first and foremost, business. Writing code is fun, but writing high quality code on time and with the least possible cost is what makes a successful software project. Given that goal, this book assumes a certain level of skill to read the code in one or more languages, and basic familiarity with building and testing software projects. It also assumes that you have at least a basic understanding of software development cycle, and how the needs of customers into the software project being tested. Who Book Is Not For: This is not a book for fresh developer level college entry-exit, or for those just starting out as a professional programmer. This is not a book about writing code ta;? It sa book about how we write code together while keeping quality up and costs down?. It's also not a book about project management or development methodologies. While specific strategies such as Test-Driven Development and Continuous Integration have risen to popularity hand in hand with Agile development methodologies, there is no link between them. There are many current projects using Scrum that do not use TDD, and there are just as many waterfall projects that do. Philosophy versus Practicality: There are many religious arguments in software development. Most of the chapters in this book relate to practical steps that you as a developer can do to improve your skills and improve the state of your project. This should be a kind of book you can pick up, read one chapter, and leave with some practical changes you can make to your software project that would make it better. There are only a practical way to do Test-Driven Development because there are ways to manage a software project. Continuous Integration is a way of thinking about your development process rather than concrete or specific techniques. The second and third part is the process more concrete and construction techniques that can improve your code and your project. Various techniques described in this book can all gradually increase one project at a time. If you start a new project and have the opportunity to determine its structure, then by all means read the whole book and see how it affects the way you design your project. Any new techniques you learn makes you a better developer, so take them one at a time and project your schedule allows. Again, this is not a book about how to write code, and examples in it all meant to illustrate a certain point, do not become part of your software projects in a literal sense. Part I (Philosophy) contains chapters that focus on abstract ideas about how to approach software projects. Chapter 1 (Buy, not Build) explains how to decide which part of your software project, you need to write your own and what part you may be able to buy or leverage from other places. Chapter 2 (Test-Driven Development) examines Test-Driven Development (or Test-Driven Design) philosophy and some practical ways to apply them in your development cycle to produce high-quality code in less time. CI involves automating your build and unit testing process to give developers a short feedback cycle of changes they make to the project. The chapters in Part II (Process) explore processes and tools that you can use as a team to improve the quality of your source code and make it easier to understand and to maintain. policy for your team to make it easier for developers to work together, and easier for developers and testers to work together. Chapter 5 (Testing) presents several concrete suggestions for how to create tests, how to run it, and how to organize them to make them easier to carry, easier to measure, and more berguna for developers and testers. Chapter 6 (Source Control) describes a technique for using a source control system you effectively making it easier for developers to work together on the same project, and is easier to correlate changes with binary source control software with physical and or publish in your disability report tracking system. Part III (Construction Code) includes chapters on specific coding techniques that can improve the quality and maintainability of your software projects. Chapter 8 (Contract, contr act, contract!) Programming deal with contracts and how that can make your code easier for developers to understand and use.