How andyfratello/pro2 works
Main Components
• Think of each top-level directory as a major module or category:
• “Apuntadors 1” and “Apuntadors 2”: Exercises focusing on pointers.
• “Exàmens”: Contains exam solution PDFs.
• “List & BinTree”: Contains exercises (including .tar archives and one .cc file) on lists and binary trees.
• “Map & Set”: Exercises concerning map and set data structures.
• “Pràctica”: Contains a practice/project assignment (with both a PDF description and program archives).
• “Sessio1”, “Sessio2”, “Sessio3”: Likely collections of session exercises or labs.
• “Stack and queue”: Exercises related to stacks and queues.
• A component for the README that explains the purpose (“Programació-2”) and serves as an entry point for understanding how the repository is structured.
Architectural Patterns
• Use a hierarchical breakdown: a top-level node for “Programació-2 Exercise Repository” that branches out into modules such as “Pointers”, “Lists & Trees”, “Maps & Sets”, “Stacks & Queues”, “Sessions”, etc.
• Such modular separation respects separation of concerns—a common design principle.
Technologies and Artifacts
• Optionally, note that the project is used for educational purposes, so the “client” is effectively the instructor/student workflow.
Instructing the Principal Software Engineer
• Pointers (combining Apuntadors 1 and Apuntadors 2)
• Exams (Exàmens)
• Lists & Binary Trees (List & BinTree)
• Maps & Sets (Map & Set)
• Practice Project (Pràctica)
• Sessions (Sessio1, Sessio2, Sessio3)
• Stacks & Queues (Stack and queue)
• Use clear labeling for each node.
• Another for modules containing archives (.tar files),
• And another for documentation or exam files (.pdf).
• Optionally, include a “Documentation/README” node linking to all other components to indicate the foundational overview provided in the README.