code.
deploy.
support.
respond.

constantly.

Our Mantra


Over our 35 years of developing, deploying, supporting, and maintaining applications that must run 24-7-365 we have developed our mantra... Hail Caesar! We believe you must define the Style Guides, Code Templates, and the Release and Support Process first... the rest is easy.

  • Style Guides and Analyzers
  • Authorless Styles
  • Templates for all Work Products
  • Standarized Workflow
view example

The Circles


Our method of customer support since the late 1980s. This is a formal process to keep Development, Deployment, Defect Correction, and App Enhancements running constantly. This is now referred to as "DevOps", "Agile Development", and "Continuous Delivery / Continuous Integration (CD/CI)" in the software industry.

  • Protect Production Critical Apps
  • Hot Fix any Build in Production
  • Carry Defect Corrections Inward
  • Respond in hours or days, not months or years
view process

Development Tools


During our VAX/VMS and Alpha AXP years we used our own "MicroCODE Development System" (MDS) which was built as a shell on top of DEC Code Management System (CMS) and DEC Module Management System (MMS). With Windows development we use a internal version of our MDS along with Visual Studio. For Web development we use Git and GitHub and Visual Studio Code with our MDS process translated into 'Git Flow'-like workflow.

  • Industrial Tools
  • Continuous Improvement
  • Standards Embraced
  • Standarized Workflow
read more

User Documentation


Both in our source code and in our user documentation we strive for consistency, simplicity, clarity, and readability. Delivered with the software from day one, we strive to document even the simplest update or release.

  • Customers can self-train
  • Issues are known and referential
  • Hot Fixes are explained
  • Release triggers are understood
view example