The Daily Build

Icon

Software Development, version 3.0

The Best Development Tools

There are two kinds of great software development tools:

  1. Those that do one thing exceptionally well.
  2. Those that allow you to communicate better with your coworkers.

In some rare cases, you may find that the same tool lives in both categories.

Without an insane focus on exactly one mission, tools get watered down and cumbersome to use.

Quick example: version control tools. When evaluating a tool, ask what else the tool is capable of. If it can also handle bug tracking, feature requests, mailing list management, continuous integration, and monitoring the coffee pot, then back away slowly. Seriously. You want a version control system that is tightly focused on its core mission and nothing else.

Yes, you need those other capabilities, but you’re better off getting them from a different tool and then integrating the two. I know, I know, it sounds like such a great idea to have everything under one roof, one vendor to contact, etc. The reality is that you end up with a comprehensive, tightly integrated set of weak tools.

Share and Enjoy:
  • del.icio.us
  • Digg
  • Sphinn
  • Facebook
  • Mixx
  • Google Bookmarks
  • Twitter
  • FriendFeed
  • Posterous
  • email

Related posts:

  1. 9 “Must-Have” Tools for Software Teams The items below are useful systems based on my...
  2. How to Tell SSH Who You Are Do you log in to several servers with different usernames...
  3. zsh history expansion Exploring zsh features made me want to figure out...
  4. Using Lenny to Build Jaunty Packages <shameless_plug> I’m in the middle of putting together packages...
  5. 3 Easy Ways to Stick to a Coding Standard When you’re writing python, you don’t need a lot...

Category: tools

Tagged:

4 Responses

  1. Mark says:

    How would you rate a tool like Accurev which is not just version control, but not full suite ALM either?

    http://www.accurev.com

    Mark

  2. brian says:

    Mark -

    I used Accurev (as an admin and developer) for five years, both VC and the integrated bug tracker (Accuwork).

    The VC part of the tool works great. Good value, awesome support, minimal training required for day to day use.

    The bug tracker is weak. We used it, and it ended up that we couldn’t really justify migrating away (it wasn’t awful).

    If you like the way Accurev does VC, buy it, but don’t use Accuwork. Use their “Accubridge” product to connect Accurev to a real bug tracker.

    I can’t speak for their other offerings as we just used Accurev and Accuwork.

  3. Mark says:

    Thanks for the fast response! That’s what we’ve heard from users as well. I’d also say they were impressed with the way Accurev managed process as well, but did recommend using Jira or another bug tracker if we needed more than the basics. New web interface looks pretty cool though. I’ll weigh it in.

    Thank you again.

    M

  4. Ken Olofsen says:

    Great post, couldn’t agree more!!

    I’m with Atlassian and we have a great set of development tools, but we would never consider them a suite. As you say, the best development tools are built for a single purpose, not just to complement something else.

Leave a Reply

About Me

Related Posts

Related posts:

  1. 9 “Must-Have” Tools for Software Teams The items below are useful systems based on my...
  2. How to Tell SSH Who You Are Do you log in to several servers with different usernames...
  3. zsh history expansion Exploring zsh features made me want to figure out...
  4. Using Lenny to Build Jaunty Packages <shameless_plug> I’m in the middle of putting together packages...
  5. 3 Easy Ways to Stick to a Coding Standard When you’re writing python, you don’t need a lot...