What is the best way to build architecture?

Question

Game development

I'm doing my text quest similar to this (I recommend turning off the sound on YouTube in advance).
The goal of the project is to make the architecture humane for the first time (so that the application is scalable and new functionality can be added easily), deal with Zenject, and publish for the first time.
In the video, we see that, at its core, the game consists of different messages that pop up
to the user.
About the implementation:
The scene itself was implemented in the form of such a ScriptableObject, in order to create and configure new replicas it was possible immediately in the editor.
To show the scene, a window was assembled on UI elements, on which hangs like thisscript. It parses the SO passed to it, after which the window pops up.
There is also a third entity - the window manager. It should essentially become the entry point into the game. Depending on the history chosen by the user, he must start with one or another ScriptableObjecta. It sends some option to the first window, the window shows it. When the user clicks on one of the options, the button generates an event and returns its index to the window (each button with an answer option has its own unique index.). The window, in turn, returns the index of the pressed button to the window manager, after which the window manager launches the next option in another window. And so it goes throughout the game.
I guess I overdid it. I would like to do everything as SOLIDLY as possible, but I, apparently, do not understand the essence. I will be glad to any councils and remarks. And if someone agrees to share their experience on Skype, I will be triple grateful.

Answer 1

The goal of the project is to make architecture human for the first time

What is human architecture?
Almost every programmer has faced the fact that looking at his code 6-12 months ago, he wants to rewrite everything from scratch.
And a year later, the same thing happens with the new code.
The essence and not understand until you step on a rake.
If this is a home project for you - I would suggest to spit on all the rules of good code, and write as you like - no comments, no MVC, no SOLID principles, etc. Then, stepping on the rake of your shit code, you will:
1. Understand why you need to do it this way and not otherwise
2. Rewrite your code more correctly
The most important thing that you will get in this approach is a lot of experience. And a real understanding of why it is necessary to do so, and not otherwise.