Operator Calculus, Co.

An Oakfield practice

Oakfield Software

Bespoke applications and the systems needed to operate them.

Oakfield Software is David Kirby’s software and systems practice, with a current emphasis on financial clients and internal business applications. The work draws on independent practice since 2001, across telecom, enterprise systems, commerce, agencies, and financial software.

Plan view of the dry-air refrigerating machine, including the flywheel and connected machinery.
Dry-air refrigerating machine, plan view. An archival illustration, not an Oakfield project. Scientific American Supplement, 1881. Source

Applications & infrastructure

  • Financial applications: specialist workflows, calculations, and interfaces that make assumptions available for inspection.
  • Internal business systems: applications shaped around the people, data, and processes of an organization.
  • Integration & legacy systems: connecting existing tools, recovering system knowledge, and making changes to software a business already depends on.
  • Infrastructure & technical advisory: hosting, networking, deployment, operational review, and guidance for teams building their own tools.
  • AI & measurement: integrating model-assisted features, analytics, and reporting into an application’s existing workflow.

From the Oakfield Gazette

How I Work

I enjoy solving problems that span multiple domains, particularly those that do not fit neatly within the boundaries of a single profession. Much of my work involves making connections between disciplines that are ordinarily practiced in isolation. An idea from mathematics might find its application in manufacturing; a lesson learned repairing an old machine might inform the architecture of a software system.

An engraved hand holding dividers and rulers.
Hand with drafting tools. Printing specimen No. 4107, circa 1892. MacKellar, Smiths & Jordan Co., Philadelphia. Source

I am drawn to difficult, unfamiliar problems, especially those for which there is no established method or obvious solution. I like to understand how things work, why they were built the way they were, and what assumptions informed their design. Often this means studying the history of a problem before attempting to solve it. There is a great deal to learn from the successes and failures of those who came before us.

Ideas and experiments

My approach is experimental and practical. I prefer to build something small, observe its behavior, and refine it through successive iterations. Sometimes that means writing software or developing a mathematical model. Other times it means taking apart a machine, studying a schematic, interviewing a specialist, or working through a problem with pencil and paper. I am comfortable moving between abstract ideas and physical work, and I find that each improves my understanding of the other.

I have little allegiance to particular technologies or methodologies. The best solution may be a sophisticated new system, a modest improvement to an existing process, or a return to a method that has worked reliably for fifty years. I care more about understanding the problem and producing something useful than about the novelty of the approach.

Working with others

Above all, I enjoy working with people who know things I do not. Some of the most productive work begins with a conversation between people who approach the same problem from entirely different directions. Oakfield exists, in part, to make room for those conversations—and to turn the interesting ones into actual work.

Modeling work connects to Oakfield Mathematics. Teams developing their own technical capability can also explore the Applied Infrastructure Conservatory.

Read in the Gazette: How I Work

Working together

Discuss an application, workflow, or existing system.

Tell David what you’re working on, the help you need, and any relevant timing or constraints.