Our Process

Custom software is opinionated. It is a dedicated tool rather than a generic catch-all, a screwdriver rather than a Swiss army knife. It starts and ends with real people acting in distinct environments to achieve specific aims. As developers, the better we can grasp these factors from the start, the better the results. All our projects begin with an in-depth investigation of the software goals, tasks, users, and computing environments. In other words, we seek a clear and complete understanding of the software’s ends.

We call this perspective-taking, an attempt to see the world through our clients’ eyes, to get inside their heads, to understand their perspective. We try to achieve both an intellectual attunement of the objective circumstances and situational empathy for the people using the software in their actual computing environments. We believe there are both intellectual and emotional dimensions to creating software! The better software “fits” its users in their specific environments, the better they work, and the higher the ROI for organizations. We spend lots of time listing and asking questions at the start, gathering knowledge, achieving perspective. Considerably more than most other software development companies. We believe the results make it worth it. There is great wisdom in the carpenter’s adage, “measure twice, cut once.”

We don’t put fingers to keyboard until we know what we need to do. Coding starts after we achieve perspective, after we know the software ends. Once we know we are spending time on the right things, we can focus on doing them right. A clear sense of purpose and an understanding of goals is essential, but so too is proper execution. An excellent strategy requires efficient tactical execution. In the words of Sun Tzu, “Strategy without tactics is the slowest route to victory. Tactics without strategy is the noise before the defeat”.

For us, good “tactics” means exercising proven, professional software practices, the consistent application of good programming principles, practices and techniques. Techniques such as rigorous unit testing, principles such as the separation of concerns, and DRY coding practices. We share these principles with people we admire and companies we benchmark against. Some of us have even taught these techniques to others at the university level. Clean, robust code is our goal, code that other programmers can effortlessly read, understand, and build upon. The way we begin the software development process with comprehensive perspective-taking is unusual, our “strategy” is unique. But our tactics, the way we write code, is based on common standards. It is deliberately NOT unique. We don’t write idiosyncratic code!

The old proverb “the proof of the pudding is in the eating” is just as applicable to software development as it is in the culinary arts. Ultimately, the success of custom software is measured by the people using it. For that reason, we practice an iterative development process and strive to create prototypes rapidly and have real users take it for a spin early in the development process. We listen carefully to their feedback and incorporate elements that improve the efficacy. We typically have four stages of software release: alpha, beta, pre-release, and production. Each stage accompanied by user-testing, with a gradual increase in the number of users culminating in the final production release.