Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required.
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
Coder to Developer: Tools and Strategies for Delivering Your Software 1st Edition
—Gregory V. Wilson, Dr. Dobbs Journal (October 2004)
No one can disparage the ability to write good code. At its highest levels, it is an art.
But no one can confuse writing good code with developing good software. The difference—in terms of challenges, skills, and compensation—is immense.
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.
- ISBN-10078214327X
- ISBN-13978-0782143270
- Edition1st
- PublisherSybex
- Publication dateApril 9, 2004
- LanguageEnglish
- Dimensions7.5 x 0.68 x 9.02 inches
- Print length352 pages
Similar items that may deliver to you quickly
Editorial Reviews
From the Back Cover
—Gregory V. Wilson, Dr. Dobbs Journal (October 2004)
No one can disparage the ability to write good code. At its highest levels, it is an art.
But no one can confuse writing good code with developing good software. The difference—in terms of challenges, skills, and compensation—is immense.
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
About the Author
Product details
- Publisher : Sybex; 1st edition (April 9, 2004)
- Language : English
- Paperback : 352 pages
- ISBN-10 : 078214327X
- ISBN-13 : 978-0782143270
- Item Weight : 1.2 pounds
- Dimensions : 7.5 x 0.68 x 9.02 inches
- Best Sellers Rank: #3,670,406 in Books (See Top 100 in Books)
- #1,314 in Software Design & Engineering
- #3,867 in Computer Programming Languages
- #4,766 in Software Development (Books)
- Customer Reviews:
About the author

Discover more of the author’s books, see similar authors, read book recommendations and more.
Customer reviews
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
Learn more how customers reviews work on Amazon-
Top reviews
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
If you consider yourself more of a software developer already, I recommend reading The Pragmatic Programmer: From Journeyman to Master instead. Despite being written four years earlier, that book is written in a much more timeless manner by focusing on concepts and ignoring the tools of the day.
The author covers project planning and setup from spec to code storage in chapters one to three. Chapters four and five cover some good practices with .NET code. Chapters six through eight; .NET tools. Chapters nine and ten; bug tracking in .NET. Chapter 11 is how to work with people. Chapters 12 and 14 documentation and licensing. Chapter 13 and 15 build and deployment of .NET projects.
At the time of it's writing this book would have been great for a developer who was fresh out of college and starting a .NET job. I often found myself thinking, "Yep, I do that because learned the hard way". I also found myself skipping sections when author mentioned a specific tool.
I wish I could give this book a good review. Had I read this when it came out I would have given it five stars. Now it's worth at most a skim of the good chapters.
This book is a great introductory text into general programming techniques: take advantage of your IDE, use tools that complement your IDE, use test driven development, map out a project, team development, track your time, etc.
Almost all the subjects deal with programmer professionalism. Subjects that we take for granted that no one really writes about and most programming texts do not delve into: leverage your tools, look for resources beyond the accepted tool set. Will this make you a top notch programmer? No, but it's like having a break room conversation with a programmer ace and realizing that what you do could be a lot easier.
If you're not a novice programmer, I'd strongly suggest looking over the text before purchasing.
It would, I think, be useful for a novice programmer, or someone fresh out of school who's been working on class assignments, rather than real-world projects.
The author is focused on individual or small-team development, but I would have liked to have seen quite a bit more on design and development processes.
Mike finds the right depth in the book, not too deep into the technical details, nor so abstract as to be an architectural tome for the ages. When it comes to coding the book is primarily focused on C# on the .NET platform, but you should let that dissuade you. He covers a wide variety of techniques and technologies and the book is valuable for anyone involved in the engineering side of the software industry.
The book follows the rough timeline of application development, from nailing down the feature set in the first chapter to delivering the product in the last chapter. The book is fairly brief (roughly 300 pages). Chapter by chapter:
Chapter one covers planning out your project. It covers gathering requirements and how to decide on a development methodology for the project. It gives a decent overview of all of the popular development methodologies and pointers as to where to learn more. It also covers some software that you probably didn't know was out there but that can help you as you nailing down the feature set.
Chapter two covers architecture and gives a nice overview of both the UML and Patterns side of the business, and the more fast and loose XP development process.
Chapter three covers source code control and it's one of the best chapters in the book. When I got through chapter three I knew already that the book was worth the purchase price. This chapter covers in a very concise manner the best practices of source code control and the products that are available on the market.
Chapter four is a brief introduction to sane coding practices; using tools like assertions and exceptions, and how to comment code effectively.
Chapter five gives a high level, but insightful, summary of the unit testing, system testing, and the technique and benefits of test driven development. This is one of the best chapters.
Chapter six covers the IDE and how to make the best use of it. This is a fairly Microsoft specific chapter, but you can learn some tricks that are applicable to other development environments.
Chapter seven covers a topic which is often ignored, the skill of digging into code at the system level and finding your way around. This one is definitely .NET specific, and it was a little too low level for me. Your mileage may vary.
Chapter eight covers code generation, a topic near and dear to me. It's a very practical chapter introduction and should save .NET developers a lot of time.
Chapter nine is about bug tracking and fixing. As with the rest of the chapter this is a concise introduction to the topic that gives you a feeling for the benefits of bug tracking, which should be obvious, and advice about tools and process. Once again I have never seen a book that provides a good argument with the brevity of Mike's writing style. Code Complete, for example, covers this stuff, but it's thick and impenetrable. This book gets right to the core of the topic and presents it in a very accessible way.
Chapter ten covers logging, which can be overdone. Again pragmatic and practical advice. But this chapter is fairly .NET specific.
Chapter eleven is about the dynamics of small teams. He introduces Instant Messaging, Wikis, and group ware. A nice introduction, but a bit brief.
Chapter twelve is about both end-user and code documentation and the tools to develop it quickly.
Chapter thirteen covers the build process. The tools are fairly .NET specific (nant), but the process and the methodology are appropriate to any production software development shop. Another nice chapter with content you will be hard pressed to find in such a concise form anywhere else.
Chapter fourteen is about licensing. This is important for open source developers. It has a nice comparison of the popular open source licenses and makes sense of all of the legal gobbledygook.
Chapter fifteen is about installers and application delivery. It's primarily for .NET desktop application developers.
There is an old story about a developer that is walking out of a tech show empty-handed, he says to the security guard that he 'Stole a fortune'. The security guard, puzzled, asks, 'But you have nothing.' The developer responds that he now has new ideas! This is that kind of book. It's full of ideas for the software process, ideas about how to code, and ideas about tools you can use.
If you are an engineer who is passionate about his craft, this is an important book for you to read. But you probably know that already.
Top reviews from other countries
In a simple, no-nonsense style, it guides you through the essentials of planning, managing, deploying and selling your software. I develop asp.net websites and have found this book extremely useful to follow "good practice" in my development process.
I does not advocate expensive software and spells out in detail the pros and cons of the various software solutions it mentions (eg. for source control, bug tracking, build management etc).
The author writes from personal experience and is obviously aware of the issues faced by lone developers or small development teams on a tight budget. The book gave me a good grounding in best practices, something which other programming books assume that every developer already knows.
There are several chapters that especially deal with Visual Studio .NET, how to pump up the IDE, which add-ins to get... complete with prices, this is information that will be out of date in less than a year.
Only somebody who comes straight from college and has only had some small introduction to coding or someone who hasn't been programming for >10 years AND is stuck on the .NET platform _might_ benefit from it.






