How iyy0v/usthb-projects works
Project type and purpose
• At the highest level, this repo is a “portfolio” monorepo of independent university projects spanning multiple years (L1, L2, L3, M1, M2).
• It is *not* one single runtime system but rather a categorized collection of small standalone systems: algorithm exercises (C), object-oriented Java apps, web mini-sites (HTML/PHP/JS), SQL scripts, compilers (Flex/Bison/C), OS/assembly experiments, a multi-tier distributed application, etc.
File structure
• Top-level folders:
• L1, L2, L3, M1, M2 (year-level groupings).
• README.md (overview).
• Under each year you find one or more *projects*, each in its own subfolder (e.g., L2/A3marDarek, M1/PCL_Compiler, M2/DistributedApp, M3/TabGen).
• Each project folder contains exactly the source, binaries, scripts and documentation needed for that standalone assignment.
• There are no cross-module dependencies—each project compiles/runs independently.
README for additional insights
• The README enumerates each project, its abbreviation, its tech stack, and the learning goal.
• Technology summary by year:
• L1/L2: C algorithmics + Assembly + Java console apps
• L3: Python/NLP, mini-compiler, PHP web, shell-clones
• M1: Web (HTML/CSS/JS/XML), sorting benchmarks (C), OS scripts, SQL (Oracle), JUnit tests, compiler with Flex/Bison
• M2: Distributed N-tier (EJB3, sockets, RMI, MySQL), Data Warehousing (SQL), Java design patterns
Diagramming conventions
• Use clear labels on every node (“L1 – Algo Scripts”, “M2 – DistributedApp: EJB Server”).
• Rectangles for folders/modules
Detail without overthinking
• *Level 2* (optional deeper dive): pick 1–2 key projects (e.g., PCL_Compiler, DistributedApp) and expand their internal architecture
• *all* essential components (source code, build scripts, docs, binaries) at whichever level you present