Does your team spend days integrating code at the end of a project? Does your team spend more time fixing bugs than writing code? Does it seem like something breaks every time you download the latest code? Continuous Integration can help. Using Continuous Integration will eliminate that end-of-project integration stress, and at the same time will make your development process easier, simpler, and with fewer surprises. But Continuous Integration is more than just a tool like CruiseControl.Net; it is a full development process designed to reduce bugs, increase visibility of project status throughout your team, and to streamline code deployments to QA or to your client. Find out what Continuous Integration is all about, and what it can do for you.

Bio

Jay Harris is a .NET developer and independent software consultant in South-East Michigan, and has been developing on the web for 15 years, since he abandoned VB3 for JavaScript to avoid waiting for a compile. Building on experiences a young lad, watching his grandparents struggle to program the VCR, he has focused his development efforts on creating a fast, reliable, and intuitive user experience, and is a strong advocate of patterns and practices that improves UX through code, ranging from automated testing and continuous integration to designing applications around a user instead of around a database. Jay is also active in the developer community,serving as President of Ann Arbor .Net Developers (http://www.aadnd.org) and as an organizer for Lansing Give Camp. When he is not coding, Jay is usually blogging to http://www.cptloadtest.com or playing games on his Xbox 360.