This project started in early 2009. From January to September of that year I've decided to take a step back from focusing on specific technology and spend time thinking about some of the observations I've made over the previous years on programming and building systems.

Some of the things I was trying to figure out had to do with noticing that many projects I've seen or worked on were building from scratch very similar tooling that existed in either the OS, or other various central management systems - things like user/role management, authentication, the authorization model based on application features expressed as metadata. Other tools - document version management for example, available to developers - were similarly reinvented by them from scratch to various degrees of quality in many of the projects any developer is probably familiar with. Other functionality included reporting, analytics, the management of the various concepts the business domain required.

The main driver for the things I've set to think about then was this question: To what degree can the business components and the technical implementation of a system be decoupled, allowing different roles to better collaborate on a dynamic, evolving system ?

Then in 2014, I've started to look into Angular and looking for an app to implement to learn Angular I've started to work on what became this project.

In total I have spent a few hundred hours in 2009, and between 2014-2018 rewriting a few times the code from scratch and in the process learned NodeJS, React, Typescript, ES6, webpack and a few other things, and with each steps learned a bit more about how various parts of such a system interact with each other.

This has been a very experimental project and I have enjoyed a lot working on it, and as a result found a new appreciation for the challenges language designers face when designing and evolving the semantics of real world languages.