DCI - How to get ahead in system architecture


Details
Welcome to ÖDM's next meetup!
This time Andreas Söderlund (https://github.com/ciscoheat) will talk about DCI
DCI stands for Data, Context, Interaction. The key aspects of the DCI architecture are:
• Separating what the system is (data) from what it does (function). Data and function have different rates of change so they should be separated, not as it currently is, put in classes together.
• Create a direct mapping from the user's mental model to code. The computer should think as the user, not the other way around.
• Make system behavior a first class entity.
• Great code readability with no surprises at runtime.
The host for this meetup is: Clavister.
Material for this meetup (and previous meetups)
—
On this page https://jrbaudin.github.io/odm-awesome-list we collect all relevant information for these meetups. For example Demo-repos, presentations, links, etc.
Book Wednesday the 15th of november in your calendar and we'll see you there!
Questions, thoughts and discussions can easily be had here on meetup.com (https://www.meetup.com/ovik-dev/) or on the Facebook page (https://www.facebook.com/groups/117816668796460).
More information regarding this meetup will come!
PS. Remember to join our group on Slack by requesting an invite here: https://ovikdevmeetup.now.sh (https://ovikdevmeetup.now.sh/)

DCI - How to get ahead in system architecture