Do you believe continuous performance can benefit the code your development team produces? What obstacles do you anticipate in implementing the practice?
Continuous Performance: A Best Practice to Ensure Faster Code
Continuous performance is a new practice for detecting and fixing performance problems from the early stages of software development. Learn how to implement this process, which drives code that's cleanly factored and easier to read and maintain.
by Cliff Sharples
July 31, 2003
ontinuous integration is the practice of conducting code builds at least once a day to catch small integration problems before they grow into show stoppers. The more often programmers test a fully integrated system, the more opportunities they have to check the functional integrity of their applications—which leads to better products. Development teams all over the world are adopting this best practice.
Continuous integration also has a hidden benefit: it sets teams up to find and fix performance problems. The trouble with performance is nobody cares about it until there's a problem, and by the time a performance issue makes its presence known it's often very difficult to find and fix. Programming teams who practice continuous integration have the advantage of being able to test performance on a regular and automated basis.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!
