Freedom as Code

A common focus of software development companies is to define everything as code (text). Rather than using a graphical interface to make some change, it’s often better to define the change as code. This enables the change to be reviewed by teammates, tracked through time, documented as part of a unit of work, tested for correctness and standards compliance, proven in a testing playground, and finally executed in a controlled way that ensures positive progress.

This gives rise to phrases like “infrastructure as code”, where the servers used by a company are all defined and configured using code. Creating a new server just requires increasing a “count” integer. Increasing memory on a database can be tried in a testing environment before attempting it on a production server.

This appraoch is required for developing complex systems because it increases objective quality and ensures that important goals are met.

It stands to reason that if we want to be successful in our quest to change our freedom, we should attempt to express it as code.

This allows us to review our freedoms, improve them over time, commission their creation and refinement, document best practices, test them, and actually determine them.

I’m gearing up to launch the project in order to explore some possibilities in expressing freedom as code.

If you’d like to support this project, please donate.