Coder to Developer: Tools and Strategies for Delivering Your Software
Coder to Developer 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:
- Choosing and using a source code control system
- Code generation tools–when and why
- Preventing bugs with unit testing
- Tracking, fixing, and learning from bugs
- Application activity logging
- Streamlining and systematizing the build process
- Traditional installations and alternative approaches
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 must build successful software projects, it’s essential reading.


Highlights include
When developers build software, they’re able to keep track of all the different versions and all the components they use with software configuration management (SCM) systems. One of the more popular SCM products is Perforce.Authored by Perforce’s own VP of product technology, Practical Perforce is the ideal complement to the existing product manual, focusing less on the ‘how” and more on the “why” and “when.” The book is not only a helpful introduction to Perforce, it’s an enlightening resource for those already familiar with this versatile SCM product. Whether you’re a programmer, product manager, or build engineer, you stand to benefit from the many insider tips and ideas presented in this convenient guide.
This book doesn’t tell you how to write faster code, or how to write code with fewer memory leaks, or even how to debug code at all. What it does tell you is how to build your product in better ways, how to keep track of the code that you write, and how to track the bugs in your code. Plus some more things you’ll wish you had known before starting a project.Practical Development Environments is a guide, a collection of advice about real development environments for small to medium-sized projects and groups. Each of the chapters considers a different kind of tool - tools for tracking versions of files, build tools, testing tools, bug-tracking tools, tools for creating documentation, and tools for creating packaged releases. Each chapter discusses what you should look for in that kind of tool and what to avoid, and also describes some good ideas, bad ideas, and annoying experiences for each area. Specific instances of each type of tool are described in enough detail so that you can decide which ones you want to investigate further.
Most IT projects fail to deliver, on average, all IT projects run over schedule by 82%, run over cost by 43% and deliver only 52% of the desired functionality. Pretty dismal statistics. Using the proven methods in this book, every IT project you work on from here on out will have a much higher likelihood of being on time, on budget and higher quality.This book provides clear, concise, information and hands-on training to give you immediate results. And, the companion Web site provides dozens of templates for managing IT projects. You don’t need an advanced degree in project management or a black belt in Six Sigma methodologies to improve your IT project results. What you need is a clear, concise and easy-to-implement system for managing all IT projects.









