Avoiding ALM ADD: Perforce, Mylyn, and Eclipse

by David Shepherd, April 24th, 2011

Software developers leverage many supporting technologies to get their own work done and to coordinate their activities with others. Developers use issue-tracking systems to organize tasks, SCM systems to store source code, and an IDE to write code. As developers use these disparate technologies it’s easy for them to develop ALM ADD. They switch to the issue tracking web UI to determine what task to do next, open the IDE to work on that task, and use a command-line client to check-in the newly created code. They code for a few minutes and then reopen the web UI to retrieve a code snippet. The constant switching, inability to focus, and distraction that is a hallmark of this workflow kills developers’ productivity. It causes otherwise productive programmers to forget relevant details and struggle to stay on task. Fortunately, through tool support this development disorder can be avoided.

Perforce

In our upcoming joint webinar with Perforce we’ll be showing how to use Perforce and Mylyn to stay inside of Eclipse as you work. Instead of switching from IDE to browser to command-line, we map out a IDE-centric approach. Of course, bringing the ALM tools into the IDE avoids switching, but it also enables some deeper integration across the ALM stack such as automatically creating change-sets for tasks. Sound interesting? Join us by registering for the webinar that Perforce’s Randy DeFauw and I will be holding on Wednesday, April 27, 2011, 11 AM PDT / 2 PM EDT.

2 Responses to “Avoiding ALM ADD: Perforce, Mylyn, and Eclipse”

  1. Norbert Colon Says:

    Perforce and Mylyn? Why would anyone use that instead of Git and Mylyn? Remember what Linus said… http://www.youtube.com/watch?v=4XpnKHJAok8

  2. David Shepherd Says:

    Norbert,
    Thanks for bringing up this question! Git certainly the most popular newcomer to the SCM space and it’s natural to ask “Why not Git?” While Tasktop is focused on supporting Git (and other newer ALM tools) we also have a long tradition of supporting the tried-and-true solutions. We’ve found that supporting both established as well as cutting-edge tools allows all types of developers to flourish. Those that prefer robust tool support hardened by years of usage can leverage established tools like Perforce and P4 for Eclipse. Those that want a distributed SCM and are willing to wade through a UI and code base that are still under active development can use Git and eGit for Eclipse. An interesting side point, which we’ll discuss during the webinar, is that Perforce + Tasktop provide the developer with many of the same workflows that Git and eGit provide. Hope you can join us on Wednesday!

Leave a Reply