Yes, I'm going to add more detailed recommendations and provide a list of found architectural issues.
About Stable/Unstable components - I use terminology suggested by Robert C. Martin in Clean Architecture book, he calls components "stable" when they're used a lot by other components. It means that these components are difficult to change because any change could have a big impact on the whole system. That makes them "stable" and dangerous.
"Unstable" component is a component that easy to change, it does not affect others, because there are much less dependent components.
Probably, I need to change these terms to something more clearly and less confusing.
Thank you for your comment James
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yes, I'm going to add more detailed recommendations and provide a list of found architectural issues.
About Stable/Unstable components - I use terminology suggested by Robert C. Martin in Clean Architecture book, he calls components "stable" when they're used a lot by other components. It means that these components are difficult to change because any change could have a big impact on the whole system. That makes them "stable" and dangerous.
"Unstable" component is a component that easy to change, it does not affect others, because there are much less dependent components.
Probably, I need to change these terms to something more clearly and less confusing.
Thank you for your comment James