How dov4k1n/seminars-evm works
Main components
• Academic/Project Groups – treat each top-level folder (e.g., “1-semester”, “2-semester”, “3-semester”, “4-semester”, “caos”, “tba”) as a major subsystem.
• Within each semester folder, there are many projects grouped by topics (for example, in “1-semester” you see projects like “01-hello-world-and-calculator”, “02-conditionals-and-cycles”, etc.). Consider representing each project as a node within its semester group.
• Auxiliary components – elements such as build configurations (Makefiles, CMake files) or tool integrations (like the use of external libraries in some projects such as nlohmann/json) can be noted within the appropriate group.
Out Relationships and Interactions
• Since most of these projects appear to be self-contained and are not part of a single running application, the “data flow” is minimal at a system runtime level. Instead, view this as a portfolio or learning repository.
• A container (or repository) at the highest level that holds multiple independent subsystems (themselves each a collection of standalone C/C++ projects or experiments).
Architectural Patterns and Design Principles
• Projects with a specific design (such as the “1-theater_cpp” in the “tba” folder) would benefit from showing class dependencies, if necessary.