Details

Foreword. <p>Introduction.</p> <p>Chapter 1: Planning Your Project.</p> <p>Chapter 2: Organizing Your Project.</p> <p>Chapter 3: Using Source Code Control Effectively.</p> <p>Chapter 4: Coding Defensively.</p> <p>Chapter 5: Preventing Bugs with Unit Testing.</p> <p>Chapter 6: Pumping Up the IDE.</p> <p>Chapter 7: Digging Into Source Code.</p> <p>Chapter 8: Generating Code.</p> <p>Chapter 9: Tracking and Squashing Bugs.</p> <p>Chapter 10: Logging Application Activity.</p> <p>Chapter 11: Working with Small Teams.</p> <p>Chapter 12: Creating Documentation.</p> <p>Chapter 13: Mastering the Build Process.</p> <p>Chapter 14: Protecting Your Intellectual Property.</p> <p>Chapter 15: Delivering the Application.</p> <p>Index.</p>

<b>Mike Gunderloy</b> is the lead developer for Lark Group, Inc., an independent software consulting firm in eastern Washington. He has worked with Microsoft data access and web technologies for more than a decade. He is the author of <i>ADO and ADO. NET Programming</i>, and co-author of <i>.NET Programming 10-Minute Solutions</i>, <i>Mastering Visual C# .NET</i>, <i>.NET E- Commerce Programming</i>, and the best- selling <i>Access 2002 Developer's Handbook</i> series, all from Sybex.

"<b>Two thumbs up"</b><br /> <b>—Gregory V. Wilson,</b> <b><i>Dr. Dobbs Journal</i></b> <b>(October 2004)</b> <p>No one can disparage the ability to write good code. At its highest levels, it is an art.</p> <p>But no one can confuse writing good code with developing good software. The difference—in terms of challenges, skills, and compensation—is immense.</p> <p><i>Coder to Developer</i> helps you excel at the many non-coding tasks entailed, from start to finish, in just about any successful development project. What's more, it equips you with the mindset and self-assurance required to pull it all together, so that you see every piece of your work as part of a coherent process. Inside, you'll find plenty of technical guidance on such topics as:</p> <ul type="disc"> <li>Choosing and using a source code control system</li> <li>Code generation tools—when and why</li> <li>Preventing bugs with unit testing</li> <li>Tracking, fixing, and learning from bugs</li> <li>Application activity logging</li> <li>Streamlining and systematizing the build process</li> <li>Traditional installations and alternative approaches</li> </ul> To pull all of this together, the author has provided the source code for Download Tracker, a tool for organizing your collection of downloaded code, that's used for examples throughout this book. The code is provided in various states of completion, reflecting every stage of development, so that you can dig deep into the actual process of building software. But you’ll also develop “softer” skills, in areas such as team management, open source collaboration, user and developer documentation, and intellectual property protection. If you want to become someone who can deliver not just good code but also a good product, this book is the place to start. If you <i>must</i> build successful software projects, it’s essential reading.

US