General Software Development Track
 

D1: Introduction to Eclipse – Dave Limbaugh, Priority Health

Eclipse is an open source community whose projects are focused on building an extensible development platform, runtimes and application frameworks for creating, deploying, and managing software across the entire software lifecycle. Many people know Eclipse as a Java IDE, but Eclipse is much more than that.
 

This session will introduce you to the power and flexibility of Eclipse. While we’ll touch on some of the 900+ plugins available for Eclipse, we will primarily focus on demonstrating the use of Ecplise for Java, C++, Ruby, Python, Perl, and PHP.
 

D2: Continuous Integration: What, Why and How – Joel Ross, NuSoft Solutions

The next release is looming in the distance, and you’re responsible for integrating the changes for all of the developers on the team. Last time, it took all day just to get it to compile. There’s got to be a better way! In this day and age of Agile software development, release cycles are getting shorter and shorter. As the build cycle gets squished, it’s imperative that a team doesn’t waste days at a time creating a build. Using Continuous Integration, development teams can “feel the pulse” of their project and be sure that builds aren’t a major headache. In this session, we’ll look at how a team can use continuous integration to enable quicker and easier builds, garner faster end user feedback, perform automated testing, and make deployments faster. Then we’ll dig into some of the common tools used to make continuous integration possible, followed by a demonstration of creating a simple, extendable build process.
 

D3: An Automated Mock Object Generator for C++ – Scott Miller, Atomic Object

Interaction-based unit testing using mock objects is becoming very popular. Libraries to generate mock objects exist for many platforms and languages, but C++ seems to be a notable exception. This talk presents a library that generates mock objects directly from the definition of an interface in C++ code. Using these generated mock objects, a C++ developer can set expectations and verify the interaction of classes and objects in a manner very similar to more modern languages.
 

This library uses a combination of code generating python scripts and a few class definitions in generic C++ to provide the functionality of recording expectations, playing those expectations back during the exercise of a method under test, and verifying that all expectations were met correctly.
 

We will be discussing the testing issues that led us to create this tool, how mocking for the purpose of performing interaction-based unit tests works, and some of the specifics of how this library successfully handled the workload.
 

After attending this session, you will have a better understanding of how mocks do what they do, and why. You will also receive the fully functional mock generator to examine or use in your C++ projects.
 

D4: Clean Code – Robert Martin, Object Mentor

Keeping code clean is a simple matter of professional ethics. In this talk, Robert Martin shows how a Java module can start clean, become messy, and then be refactored back to cleanliness. Be forewarned: this class is about CODE. We will put code on the screen, and we will read and critique it. And then, one tiny step at a time, we will clean it. You will participate in the step-by-step improvement of a module. You will see the techniques of the Prime Directive (Never Be Blocked), and Agile Design Principles brought into play. You will witness the decision-making process that agile developers employ to write code that is expressive, flexible and clean. Finally, you learn an attitude of professional ethics that defines the software developer’s craft.
 

D5: Classical vs. Mock Test Driven Development – Carlus Henry, Sagetech LLC

After reading Martin Fowler’s article Mocks Aren’t Stubs, I started to ask myself the question if I am a Classical or Mockist Test Driven Developer, and if I needed to reevaluate my strategy to Test Driven Development. During this presentation we will be examining the difference between both styles of Test Driven Development, discover the advantages of each, as well as examining some of the Mock generating libraries available. We will also discuss the style of Test Driven Development that I chose and why.
 

D6: i18n and l10n – Adam Goucher, The Jonah Group

As more and more companies realize the potential market for their software reaches beyond areas where English is the incumbent language, the need for testing for internationalization (i18n) and localization (l10n) issues increases. So too does the complexity of implementation and the disruption of fixes. This presentation will act as a primer for people starting down the i18n or l10n road.