No nonsense.

Mallowfields builds digital tools and methods for engineering and governance. We solve problems in decision-making, knowledge-sharing, and collaboration.

We self-fund our product development through relevant service work. We offer our clients in business and government the same attributes we bring to bear on our own projects: technical depth, mature skill, efficient self-management, and a no-nonsense approach to building digital systems that actually work for the people who use and support them.



Mallowfields works as a team. Collaboration is a practical requirement to build quality software that solves more actual problems than it creates.

We are experienced masters of our trades. We are more than the sum of our parts, but our parts are formidable too. Working with us means engaging our actual, specific, human selves, with our accumulated histories of skills, knowledge, and perspectives.

Kendell Joseph

Kendell is an expert in both server and client-side JavaScript, in graph database use cases and implementations, and in geographic information systems.

His broader skill set includes computing education, Python development, data visualization, audio visual processing, and machine learning. He sometimes gets drafted for photography too.

Kendell can do it all himself (and he has), but he kills it when he builds teams that get technical work done. He can get 7th graders to build working AR applications while working against a backlog of user stories, and he can make something real with your team too.

Joshua Honig

Joshua is an expert in .NET application and service development; in relational database design, implementation, and migration; and in solution architecture for on-premise, cloud, and hybrid scenarios.

His broader skill set includes integrating, reverse engineering, and migrating legacy enterprise technologies (COBOL, MS Access, VBA/VB6, z/OS? yes); and designing and implementing complex graphical user interfaces for the web. He sometimes gets drafted for copywriting too.

Joshua can build all the parts (and he has), but he kills it with solution architecture, whether designing new systems, untangling inherited messes, or working with technical colleagues to refine and arrange a project already in progress.


Architecture First

No actual solution starts with software. Recognizing and describing the systems and environments in which we live and work — and sometimes build digital machines — is more than requirements gathering, project management, or business analysis. Clear-eyed architecture, based on combined decades of success and failures, is the foundation of all our work, no matter how small the project.

Effective systems thinking starts with recognizing the limits of designed systems. We want to quote most of Systemantics by John Gall, the greatest (only?) satire in the field of systems theory. We will settle for just two more aphorisms, which offer a grounding perspective for us as even as we do the work that we love of designing and building human-digital systems:




But are you Agile?

We actually have our own manifesto, subject to change at any time:

  • Critical thinking over manifestos
  • Actual experience over certifications
  • Vegetables over meat, unless it's smoked or incorporates bacon
  • Pragmatism over computing religion
  • Technical depth over fad-chasing
  • Actual reality over compelling narratives
  • Thoughtful architecture over enthusiastic hacking
  • Obvious over clever
  • Utility over artistry
  • Humans over systems
  • Effective teams over "ninjas" and "rock stars"
  • No nonsense

Fine Print

No Nonsense

We don't hustle. We don't fake it till we make it. We are experienced and competent in our trades, and know both the depth of our skills and their limitations. We offer the skills and knowledge that we actually have, and that's enough.

We are comfortable saying "We don't know." We recognize that some problems can't be solved by us, and some problems can't be solved at all — at least not by software. We also know how to arrange and attack problems that we can solve, whether or not code is required.


We use Google Analytics to track basic site statistics. That's it. It uses cookies and collects some anonymous traffic info which we use to understand how people enter, navigate, and leave our site. You can review Google's privacy policies in detail.