Configment – together

Configment – configure

Configment – our imaginations

Configment – our imaginations combined

Whether it’s with Legos™ or pieces of the international space station, building great things requires imagination and the creative configuration of various components. We specialize in piecing together great software to accomplish great things.

Ideals:

  • configure over code
  • rapidly prototype
  • use best-in-class cloud-based software
  • focus on UX and system interfaces
  • always be optimizing

Begin with pure imagination.

What do we want to build, together? Let’s start with “what if” and be imaginative. At the onset of a project, it’s no use getting caught up in whether it’s possible. Rather, we start by imagining the perfect system. Imagination is the natural enemy of constraint.

If a figment lives in one person’s mind, then a configment is that of our imaginations combined.

Starting off in an unconstrained design space helps identify creative ways to go about solving a system design challenge.

Incorporate design constraints and specs.

Now we’ll begin to consider practical constraints and functional specifications of the system. We’ll challenge the constraints and work toward the most spare version of the system spec.

Play with software configuration alternatives.

Getting on with it, it’s out to the web to search for excellent software that can accomplish the goals. This involves twiddling around and learning the little peculiarities of each piece. Because these pieces can often be configured together in a dizzying variety of ways, this phase seeks to limit the possible configurations to a recommended handful, each configuration with pros/cons and particular technical challenges.

Design-build iterations.

Next, we’ll move to quickly to prototype the most promising configuration. This is where all the action is. If the right components are selected up-front, then the configuration is straightforward and the integration is easy. Sometimes, one component of the system isn’t optimal, then we can try one of the alternatives identified in the earlier phase. One way or another, the system gets built with minimal code.

Test, integrate, and deliver.

By this point, the system is mostly built and it’s just a matter of doing the final integration testing. Voila. Since great software is used throughout the system, its functionality and security should improve over time. As needs change, and software providers make changes, we’ll work to keep the software updated and functional to sustain it through its lifecycle.