Continuous Integration Quotes

Developers, developers, developers, developers.

One of the advantages of having to live with JUnit for 8 years is now we can look back and see which decisions we made worked nicely and which we would have done differently.

The community of developers whose work you see on the Web, who probably don't know what ADO or UML or JPA even stand for, deploy better systems at less cost in less time at lower risk than we see in the Enterprise. This is true even when you factor in the greater flexibility and velocity of startups.

Responsible Development shares many practices with XP but the roots are different. Responsible Development's values are honesty, transparency, accountability and responsibility. These lead me to pairing, test-first, incremental design, continuous integration and so on because they support the values.

Agitator and the Agitar Management Dashboard lower the barriers to accountability in software development and increase the value of developer testing.

I used Agitator on some code I had unit-tested, and it made me a better tester. As an Agitar Fellow, I look forward to the leverage of working with an outstanding organization as together we continue to improve the value of developer testing.

Running the test suite like this allows us to catch problems when they are just introduced.

Developers, developers, developers...

In true open source development, there's lots of visibility all the way through the development process.

I am not versed in production software. I have basic knowledge, but it ends there.

Extreme programming is an emotional experience.

Today, we can tell people we have a testing process and facilities in place on a nationwide basis.

Many people think that open source projects are sort of chaotic and and anarchistic. They think that developers randomly throw code at the code base and see what sticks.

When I do programming in my free time and for my own enjoyment, I really want to have a kind of protection: knowing that when I improve a program those improvements will continue to be available to me and others in future versions of the program.

Specifically, in the software industry, progress is highly sequential: progress is typically made through a large number of small steps, each building on the previous ones.

At Imgur, we need a solid product that works on various platforms, so we're looking at iOS, Android, front end, back end, and devops.

Organizations want small changes in functionality on a more regular basis. An organization like Flickr deploys a new version of its software every half hour. This is a cycle that feeds on itself.