As thought leaders in early software quality, our monthly newsletters offer guidance to the technology community. This month we encourage your thoughts and questions as we explore Continuous Integration.
The key benefit of Continuous Integration is its ability to decrease the time between when an impact causing issue is coded and when it's discovered. Impact causing issues can be, for example:
- Defects
- Metrics exceeding predefined thresholds, such as a rise in complexity
By notifying interested parties, like developers and management, when these issues arise, they can be addressed quickly, thus saving time and money-- and increasing a software system's quality at the same time.
If you want to find defects earlier and are wondering how to enhance your current processes without losing focus on business objectives then I highly encourage you to contact us-- we'll be glad to assist you.
And speaking of Continuous Integration, we are quite excited about the pre-order availability of Continuous Integration: Improving Software Quality and Reducing Risk! Authored by Stelligent's CTO Paul Duvall, Stephen M. Matyas III and yours truly, the book is due to hit bookstores in May. Make sure you pre-order your copy now!
Finally, in an unrelated topic, but definitely noteworthy, is the availability of Groovy in Action published by Manning and co-authored by myself. For all those interested in what’s groovy about the Groovy language order your copy today!
Sincerely,
Andrew Glover
President, Stelligent Incorporated
