Considering options becomes simpler using #Vithanco. Begin by comprehending your domain initially prior to implementing significant alterations.

Found this one and immediately loved it. From Hidde Douna.

Ich liebe den Postillion!

@startupsharma Those that aren’t aren’t there long enough to notice.

@TotherAlistair This type of diagrams are called IBIS diagrams, see for example:

@TotherAlistair Let me just say that I love that you simply asked questions and even requested to tell you more instead of telling me all the obvious answers. This approach triggered many more learnings. Sometimes, I simply don’t see the woods for the trees. (Like everyone else). Thank you.

@TotherAlistair Thanks! So obvious, so often forgotten. It is about responsibilities, not about technologies, locations, etc. Otherwise the architecture is not helping but confusing.

@TotherAlistair Thanks! Actually, the “system” is the next version of the system to create this kind of #StructuredVisualThinking

@TotherAlistair In my cute little head, I was suddenly using the graph type, the central data structure of the core, on the driving side (“what can happen without side effects?”). When I did my diagram, I was asking better questions myself. What you describe here is the next challenge. ;-)

@TotherAlistair I like this one. The best definition I found so far for “legacy system” is a system without tests. So, an untested I/f is a a legacy I/f. Hopefully, the real app isn’t legacy from the outset.

Interested in change and a resulting value polarisation? This Causal Loop Diagram gives you an idea: The full article is here: #StructuredVisualThinking

Very True!

I love how much information one can bring into a single diagram: Full article: #StructuredVisualThinking

@TotherAlistair Thank you so much for your offer. I prepared an email and started thinking: most likely, I didn’t think enough about the architecture. I came to the conclusion that functional programming would be perfect for the application core. Not sure whether that is an exaggeration. 😇

@FlyingLogic Not exactly true ;-)

I assume I should just provide the type interface in an incoming port, ForCreatingGraphs, or similar. But it feels odd and to be frank, I cannot put the finger on the real wound (yet). What do you say? Why am I hesitant?

Nice to see systems thinking outside of the health sector: #StructuredVisualThinking

He is up to something. Testing might be the upcoming area for developers. More so than before. Read yourself: