Cover image for Code Leader : Using People, Tools, and Processes to Build Successful Software.
Code Leader : Using People, Tools, and Processes to Build Successful Software.
Title:
Code Leader : Using People, Tools, and Processes to Build Successful Software.
Author:
Cauldwell, Patrick.
ISBN:
9780470383117
Personal Author:
Edition:
1st ed.
Physical Description:
1 online resource (233 pages)
Contents:
Code Leader: Using People, Tools, and Processes to Build Successful Software -- About the Author -- Foreword -- Credits -- Acknowledgments -- Contents -- Introduction -- Who This Book Is For -- Who This Book Is Not For -- Why I'm Writing This Book -- Philosophy versus Practicality -- Every Little Bit Helps -- Examples -- How This Book Is Structured -- Errata -- p2p.wrox.com -- Part I: Philosophy -- Chapter 1: Buy, Not Build -- Cost versus Benefit -- Creating a Competitive Advantage -- Taking Advantage of Your Platform -- Third-Party Components -- Summary -- Chapter 2: Test-Driven Development -- Tests Define Your Contract -- Tests Communicate Your Intent -- Summary -- Chapter 3: Continuous Integration -- Integrate Early and Often -- Build Servers -- Fix a Broken Build before Integrating Changes -- Summary -- Part II: Process -- Chapter 4: Done Is Done -- Discuss Design Decisions -- Every Class Has a Test Fixture -- Each Fixture Exercises Only One Class -- Code Coverage Is High -- No Compiler Warnings -- Static Analysis Tools Generate No Errors -- Before Committing, Update -- Documentation in Place -- Summary -- Chapter 5: Testing -- Why Testing Doesn't Get Done -- How Testing Will Make You a Better Developer -- Code Coverage -- Types of Tests -- Test Automation -- Summary -- Chapter 6: Source Control -- Some Source Control History -- Picking the Right SCCS -- Organizing Your Source Tree -- Making the Most of Branching -- Summary -- Chapter 7: Static Analysis -- Using Static Analysis Tools -- Who Benefits from Static Analysis? -- How to Integrate Static Analysis into Your Process -- Summary -- Part III: Code Construction -- Chapter 8: Contract, Contract, Contract! -- Public Interfaces -- Data Contracts -- Summary -- Chapter 9: Limiting Dependencies -- Limiting Surface Area -- Dependency Injection -- Inversion of Control -- Summary.

Chapter 10: The Model-View-Presenter (MVP) Model -- Why MVP? -- What Is MVP? -- Constructing the MVP Application -- Testing MVP Applications -- Summary -- Chapter 11: Tracing -- Different Kinds of Messages -- Log Sources and Log Sinks -- Activities and Correlation IDs -- Defining a Policy -- Making Messages Actionable -- Summary -- Chapter 12: Error Handling -- Result Code Reading -- Exception Throwing -- Importance of a Policy -- Defining a Policy -- Where to Handle Errors -- Summary -- Part IV: Putting It All Together -- Chapter 13: Calculator Project: A Case Study -- Wrapping Up -- Index.
Abstract:
Code Leader: Using People, Tools, and Processes to Build Successful Software "Patrick is a pragmatist with a purist's knowledge. He has a deep understanding of what 'smells' right, and he knows when and how to find the right balance to get the job done. This philosophy of balanced 'pure pragmatism' pervades this book and makes it useful." -from the foreword by Scott Hanselman, Author of ComputerZen Blog, www.computerzen.com; Senior Program Manager, Developer Division, Microsoft Corporation Writing code is rewarding, but writing high-quality code, on time and at the lowest possible cost, is what makes a software project successful. As the role of a professional developer has evolved and taken on additional responsibilities, it is now necessary to work in concert with a team in order to improve both the process and final results of a software project. This unique book introduces a set of concrete best practices and construction techniques that can be applied to the development process and to actual code construction, so that you can confidently solve business problems rather than deal solely with pure coding tasks. Patrick Cauldwell understands that it is no longer sufficient to just write software that solves a problem; it must also be fast, scalable, reliable, and easy to use. In this reference, he explains how to build software that is of high quality at a lower cost and shares with you the practical steps you must take in order to transition from software engineer to technical lead. What you will learn from this book Practical steps you can take to combine different developmental philosophies, processes, and construction techniques into a unified approach to software Methods for deciding which parts of a project you need to write yourself versus what you can buy or reuse Tools and processes you can employ to improve source

code quality and maintainability How to create, run, organize, and measure tests, and then make them more useful to developers and testers Ways that programming by contract can make your code easier for developers to understand and use Recommended techniques for handling errors in your code that will make your application easier to debug and support Who this book is for This book is for experienced software developers who are looking to improve their development skill set and bring a higher level of discipline to a project. Wrox guides are crafted to make learning programming languages and technologies easier than you think. Written by programmers for programmers, they provide a structured, tutorial format that will guide you through all the techniques involved.
Local Note:
Electronic reproduction. Ann Arbor, Michigan : ProQuest Ebook Central, 2017. Available via World Wide Web. Access may be limited to ProQuest Ebook Central affiliated libraries.
Electronic Access:
Click to View
Holds: Copies: