Home > Articles > Software Development & Management

Q&A with Jolt Product Excellence Award Winner Paul Duvall

  • Print
  • + Share This
Paul Duvall, co-author of the Jolt Award winning book, Continuous Integration: Improving Software Quality and Reducing Risk, answers questions on continuous integration, how to get started with CI, and why to fire your "best" people.
Like this article? We recommend

Q: Congratulations on your Jolt Award for the technical books category! How and when did you get the inspiration to write Continuous Integration?

A: Thank you very much. The inspiration for the book was many years in the making. On one of the my first projects I developed common components and utilities for other software developers. On this project, I really became interested in how to not just make my life easier as a developer, but make my fellow software developers' jobs less painful as well. It was also on this project that I hung the "Integrate Button" picture in my cube - which served as the theme of Continuous Integration. I really thrive on the tenets of repeatability and consistency and, as developers, I believe we spend too much time on development infrastructure issues such as setting up IDEs, defining a consistent build process, hunting down server configuration values and other such things. Since we spend a lot of time automating our customer's process, why don't we automate our own development processes? This philosophy led me into positions where I was the developer/build guy or tech lead/build guy. I also like to share my ideas with others; I've always thought that if I find an easier way to do something, I'd like everyone else to learn from these experiences. I believe that if you keep knowledge locked inside your head, without sharing with others, you are a less valuable resource. So, it was natural that as my passion for automating development processes (using practices like CI) grew, I wanted to share it with others. This is one of the main reasons why I wrote the book. I began to cultivate the idea of writing this book while on a train from Rome to Florence, Italy in the summer of 2004 while on vacation with my brother. A lot has changed since then!

Q: Since the publication of Continuous Integration, what type of feedback have you received from the software engineering community?

A: Most people I hear from say to me time and time again that this book was long overdue as it's a core Agile practice. I also hear from people that were able to incorporate a lot of the practices we cover in the book on their projects which is particularly gratifying.

Q: Is it fair to say that the practice of CI is an emerging trend?

A: No question. It's one of the least controversial of the Agile practices, but it's still not in what I consider to be widespread use. CI provides teams a way to quickly determine the health of the software; it shrinks the time between when a defect is introduced and when it's fixed, which reduces costs. It's also an emerging trend because there's so much more we can do, particularly in what a "build" can provide. A build is much more than compilation and packaging. It's database integration, testing, inspections, deployment and even installations. A build is integrating all of the components and verifying the deployed software works as a whole.

Q: What does the future hold for CI, and why are you excited about it?

A: I see the future of CI is getting to production-ready software every day. I think that as we increase hardware and software resources, we can get closer to achieving this in reality. Regardless, if development teams regularly consider what it'd take to make their software "production-ready," their approach to developing software will change significantly. The reason I like the concept of "production-ready...every day" is that it speaks to development teams and customers in the same breath. Whether or not you actually deliver software every day is irrelevant; being production-ready enables you to make ongoing project decisions based on the reality of a working software system, not what teams intend on completing. It also logically leads teams to consider practices such as test-driven development, automating deployments, and failing builds based on thresholds such as a high cyclomatic complexity. No longer can you say "I'll get to that later."

I'm also excited to see the practice of CI move toward instantaneous integration where the type of full-featured integration I described is built into the tools so that it truly is a 'non-event' to integrate software. At a recent Agile event, I heard someone describing a scenario in which a developer types a line of code, the line is marked in red in their IDE — because it integrated that line change (in a separate environment invisible to the developer) with the rest of the developers on the project and determined that the recent change broke a call to a method that another developer had recently changed. This is the future of CI that I envision.

Q: What is the most valuable piece of advice you can offer to an organization that is investigating CI?

A: Continuous Integration is not about the Continuous Integration server. It's about development practices and — at a technical level — the automated build. The fact you can run it as a daemon/service is one way to make CI continuous, but it's such a small part of CI. I often hear teams talk in terms of their CI/build management server like it's the one doing all the work. It's not. It only provides a mechanism for kicking off a build and telling you what happened (in terms of reports, emails, etc.). Committing code often, preventing broken builds, fixing builds quickly, running fast builds: these are all effective practices toward getting the most from Continuous Integration.

Q: What does it feel like for the book to have won the prestigious Jolt Award?

A: It's been a great thrill to win the award. It was an honor to even be selected as a finalist, especially in such great company of the other finalists in the technical book category. So, winning the Jolt is just icing on the cake. It really validates all the time and effort I expended working on the book. I remember sitting in a Starbucks at 8:00pm on a Saturday evening, taking off days from work, renting a hotel in Charlottesville, Virginia for a week and even editing my manuscript while on vacation in the Outer Banks, North Carolina. I lived and breathed the book for a couple of years and it feels incredible that an elite group of Jolt judges selected my book as the winner of this award. It's very, very gratifying.

Q: Tell us more about your company, Stelligent.

A: Stelligent is an expert Agile consultancy. We help our customers create production-ready software every day. We do this through a combination of Agile techniques and practices such as Continuous Integration, Test-Driven Development, Pairing and so on. One of our key differentiators is that we don't just talk about these things, we roll up our sleeves and work with clients to deliver real solutions. We have a very practical, non-dogmatic approach toward improving our customer's ability to deliver high-quality software quickly. Stelligent is led by people like Andy Glover, co-author of Continuous Integration, and Paul Julius, co-founder of the CruiseControl CI server and Continuous Integration and Testing Conference. We share a similar passion for helping development organizations become more Agile.

Q: You once wrote a blog entry entitled, "Fire your 'best' people, reward the 'lazy' ones." Can you elaborate on what you meant, and discuss the controversy that this statement caused?

A: I know, it's a bit of a provocative title! It was based on the observation at several companies that some managers consider their best people to be the ones who can get them out of a technical jam: the "firefighter." This firefighter may stay late to fix the problem and be the hero. Sometimes, however, if you peel back the covers you'll discover that there is no time spent in preventing the problem from occurring again and that it could've been the firefighter to cause the problem in the first place. In the blog, I indicate that you need a little of both, someone that can fix problems (because problems will always occur) and prevent problems. I refer to the troublepreventer as someone who is lazy, but in a good way. Someone that doesn't like to be awakened at three in the morning to fix the latest problem because someone hard-coded a variable or duplicated code which led to a software error only a few know how to fix. I think the reason for the controversy is because some inferred that I was stating that someone must be either a troubleshooter or a troublepreventer, not both. As I describe in the blog, there should be a mixture of both...but, I believe we need more people that employ troubleprevention techniques.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020