I have many software ideas that are for my own, personal benefit. History has shown me that when I create something that I like to use, others tend to like it too. I have been helped by so much freely published content and knowledge on the internet from others, I figure I will do my little part and add to that resource. Again, open source software has helped me so much, I will also make my software open source and free to use and free to change. Along with that, comes the open source maintainer "hell". I have some ideas on that, as well as, honestly, I have the attitude that I am making stuff for MY use, to make MY life better. So use it or don't, contribute or not, up to you.

I am trying to tie together many different ideas, methodologies, concepts, and practicalities:

Living Documentation: Continuous Knowledge Sharing by Design

I read the book Living Documentation: Continuous Knowledge Sharing by Design many years ago.

• Living Documentation: Continuous Knowledge Sharing by Design @ InformIT
• Living Documentation: Continuous Knowledge Sharing by Design @ Amazon
• Living Documentation: Continuous Knowledge Sharing by Design @ O'Reilly
• The author's interview on YouTube

Literate Programming

I was introduced to this concept at some point. Not sure if I read the book or not, but still I have this concept in context.

Domain Driven Design (DDD)

Strongly influenced by Eric Evans and his blue book. Note that he always said if he could do it over, he would start with the second half of the book, as that is the concepts, and NOT the first half, which are structures.

• Domain-Driven Design: Tackling Complexity in the Heart of Software - Amazon

F# (fsharp)

Object Orientated Programming has never made sense to me. I just never got it. In my explorations, I came across Scott Wlaschin. He introduced me to the functional programming paradigm and the F# language. It started to make logical sense in my mind. You can find him with many videos on YouTube and his website.

He also published his book Domain Modeling Made Functional
This book details his Railway Orientated Programming and Lego style chaining. Also is the Type Driven Design that F# makes really easy.

Command Query Responsibility Segregation (CQRS) & Event Sourcing

Introduced and research this topic for a while after the DDD exposure. Watched pretty much everything by Greg Young. Got his book. Even watched his 6 hour long video workshops that were out there.

Agile

Went through the entire learning process of Agile, which I qualify as the capital A version, with the SCRUM, stand-ups, and all the ceremony and process.

Event Modeling

Found Adam Dymitruk's original presentation on information systems in 2019 at a user group. Been following this concept since. It incorporates the agile (lower case meaning the concepts of the original paper) with DDD and human story telling memory so bring people all backgrounds together for understanding and design.

---

Vision

I have had this vision, being influencing by all the above, to have a methodology that uses Event Modeling as the glue. I feel that a forum type software is the base of operations. Most people are familiar with how they work, how to use them, and easy enough for basic users all the way to developer and technical to use. Distilling these individual posts and topics into a wiki type document to have a spec, or source of knowledge. These special docs can be used to create the EventModel (the actual visual representation). These specs can be used by AI to generate the code (I am using JetBrains Rider and Junie). Paths can be created and displayed that are used for tests which satisfy the "example" data suggested by EM.
For implementation architecture, I am trying to use Bolero with different hosting modes to have one core codebase, and then be able to support web (including PWA), desktop on Linux, Windows, MacOS, and mobile for Android and iOS. My current method here is basing the code in Bolero (F#) and using Blazor Hybrid (with an addin for the linux desktop part) and it should all work out.

I did extensive research and experimentation on UX options. Avalonia was a big part of the that. I just hate the XAML. I have been on the internet since 1994, hence been making html pages since then, etc. So I lean towards the html/css and currently think it is still the best way to make the UX. In working in Avalonia, I got the idea of "why not use the SVG file AS the source of the UI". This comes from reducing rework. If a designer (or me) can use PenPot, Lunacy, or Figma to create the UX, why not just use what that outputs as the base for the coding needed to use in the app.

The current issue with Event Modeling is the reliance on Miro and the lack of tooling. As EM is still evolving, I feel that scope is still confusing. My thoughts are to have different "Views" of the same model, one that CAN be very high level which would be important for general users, then maybe a bit more details for business folks, then more details for a department, then even more details for a developer, etc. All the same model, just depends on what you want to see as the viewer.

There is a strong opinion that the model does not match the implementation. I feel it CAN with certain systems and views. If I can hash this out, I then have a very iterative, round robin, feedback centric system that accounts for basically everything everyone is trying to accomsih in the software development world. Maybe it won't work for anyone else, and that is OK. If it works for me, then I am able to rip through ideas and be complete.