Skip to main content

Prolog on a high level to (re/) configure modules

Prolog on a high level on top of other modules. Modules have their own state. Depending on the state, other modules are activated. This state can be saved as a form of config/application state/continuation and so on. The state can be reflected in the user interface. The user interface can change the state.
I can express the rules very simple. A decision means further implications for each module. These implications are done via Prolog.
Testing is very simple as example scenarios integrate very well. Mocking is trivial.
Prolog changes how modules talk.

Comments

Post a Comment

Popular posts from this blog

Futureproof Software

From here:  https://dzone.com/articles/the-secrets-of-futureproof-software Self-healing Self-patching, or more broadly, self-updating Backward compatibility Dynamic adaptation/ability to evolve over time Intent-based Made up of reusable futureproof components
Post a Comment
Read more

Choose Projects you do NOT do!

Inspiration from FluentC++ Choose which project NOT to work on. Be clear what you want and which projects are toxic. Keep the Hedgehog-concept in mind. Be sure that you are a) deeply passionate about the project b) the project can be the best in the world quality c) you can earn money with it If one of the three points is not met and not realistic soon don't do the project. Play around with it privately. Maybe you can pivot there so that it meets the criteria.
Post a Comment
Read more