How shrootbuck/usaco works
Project Type and Purpose
• This is a personal “algorithm‐solutions” repository, not a running service or full‐stack app.
• It holds:
• USACO problem solutions, organized by year and division (e.g., 2016/Bronze)
• Solutions for other online judges (CSES, Codeforces)
• Whiteboard PNGs (with embedded Excalidraw data, though not shown in the provided file tree)
• The README explains how to browse code and import whiteboards into Excalidraw for editing.
Top‐Level File Structure
• Root
• README.md
• 2016/ (USACO Bronze, Silver, …)
• 2018/ (USACO Bronze, …)
• CSES/ (various problem .cpp files)
• Codeforces/ (subfolders per problem ID)
• Each year or judge folder contains one subfolder per contest/division or problem ID, with .cpp solution files (and sometimes .png whiteboards).
a. Developer (you)
b. Version Control Host (GitHub remote)
c. Local Clone (your machine’s filesystem)
d. Solution Directories (2016, 2018, CSES, Codeforces)
e. Excalidraw (external editing service for PNG whiteboards)
f. Optional Online Judges (USACO site, CSES grader, Codeforces judge)
Relationships and Data Flows
• Developer ↔ GitHub: git clone, pull, commit, push
• Developer ↔ Local Clone: browse code, edit .cpp, add whiteboards
• Local Clone → Online Judges: compile & submit .cpp (to USACO/CSES/CF)
• Local Clone ↔ Excalidraw: import/export of PNG whiteboards
Architectural Patterns and Principles
• Simple layered structure:
Layer 1 – Versioning (Git/GitHub)
Layer 2 – Storage (Local directory tree)
Layer 3 – Tools (Compiler, Editor, Excalidraw)
Layer 4 – External Services (Online judges)
• Modular directories: each problem self‐contained
Technologies, Frameworks, Libraries
• Git/GitHub for VCS
• C++ compiler (g++, clang++)
• Excalidraw (for editing embedded whiteboard data)
• Any text editor or IDE