Practical Development Environments

Front Cover
"O'Reilly Media, Inc.", Sep 23, 2005 - Computers - 330 pages
1 Review

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.

Developers want to write code, not maintain makefiles. Writers want to write content instead of manage templates. IT provides machines, but doesn't have time to maintain all the different tools. Managers want the product to move smoothly from development to release, and are interested in tools to help this happen more often. Whether as a full-time position or just because they are helpful, all projects have toolsmiths: making choices about tools, installing them, and then maintaining the tools that everyone else depends upon. This book is especially for everyone who ends up being a toolsmith for his or her group.


What people are saying - Write a review

We haven't found any reviews in the usual places.


Project Basics
Project Concepts
Software Configuration Management
Building Software
Testing Software
Tracking Bugs
Documentation Environments
Releasing Products
Project Communication
Politics and People
How Tools Scale

Other editions - View all

Common terms and phrases

Popular passages

Page xxvi - Writing a book is an adventure; to begin with it is a toy and an amusement, then it becomes a mistress, and then it becomes a master, and then it becomes a tyrant, and the last phase is that just as you are about to be reconciled to your servitude, you kill the monster and fling him about to the public.
Page 19 - A plus sign (+) indicates a strength and a minus sign (-) indicates a relative weakness, either in features or usability.

About the author (2005)

Matt Doar runs Consulting Toolsmiths, a software consultancy inSilicon Valley and has extensive experience configuring andcustomizing JIRA for clients all over the world. He is an Atlassianpartner and is part of the wider Atlassian development community.He also wrote "Practical Development Environments," O'Reilly (2005)which described the basics of software tools - version control, buildtools, testing, issue trackers, automation.Matt also runs the blog http: // which has a number of similar tips, trick and examples for practical JIRA development.

Bibliographic information