This section contains my personal recommendations for tools for development environments. The recommendations are intended for projects with less than 1 million lines of source code and under 200 people involved in developing, testing, documenting, and releasing the product. The annual budget for tools probably ranges from zero to $100,000. These choices are purely personal ones made from the tools available in 2005, with no undue influences from any individual companies or projects.
If you use a tool that you feel is much better than one of the tools I've recommended, feel free to send me email about it via firstname.lastname@example.org. My own contact details are available at http://www.pobox.com/~doar.
IDE recommendations are also welcome, but rants about editors (the programs, not the people) are generally unproductive—use one that does the job for you, and learn it well.
If these recommendations are enough for you to make progress with a development environment, that's great! Reading the sections about each tool later in the book is still a good idea to get some more background, especially Choosing New Tools.
However, a development environment is more than just its tools. The discussions of the best practices and annoyances of each area in the chapters that follow will help you use each of these tools in a more productive manner.
This list of tools is for environments that can afford the effort of using tools that are still themselves being ...