How frozsgy/metu works
Project type and purpose
• This is a monolithic “knowledge‐base” or “portfolio” repository rather than a deployable application. It collects every homework, lab, exam, and assignment from multiple courses (CENG111, CENG140, … , CENG499) in METU’s Computer Engineering Programme.
• Purpose: archival, demonstration of coding evolution, and reference. There is no cross‐module code execution or a unified run/build process.
File structure
• Top-level: a flat set of directories named by course code (CENG111, CENG140, …).
• Under each course: subdirectories per assignment or lab (e.g., THE1, THE2, lab1, HW1, Project 1, etc). Files are PDFs, source code (C, C++, Python, Java, assembly, Haskell, Verilog), testers, sample I/O.
• No monolithic build scripts, no single CI/CD pipeline; each subfolder often has its own test harness or README.
• A root README.md and LICENSE.
README for additional insights
• Explains purpose: collection of homeworks across courses.
• Highlights that some subrepos (CENG334, CENG336, CENG435, CENG477, CENG453) live elsewhere for “good examples.”
Elements
• Clear labels: “CENG111,” “CENG140,” … , “CENG499,” “README.md,” “LICENSE.”
Detailed capture of essential elements
• Avoid overcomplicating: the core architecture is a directory/module hierarchy with no runtime integration.
• The goal is to show clearly how the repository is organized and how a reader navigates from the top‐level to each assignment.