How lakshit2604/cpp_practice works
Project type and purpose
• This is an educational/open-source practice repository for C++ Data Structures & Algorithms (DSA) exercises.
• There is no “runtime service” or “user-facing application” here; the core purpose is to organize, compile, and run individual DSA code samples.
File structure
• Top-level:
• Patterns.cpp – a standalone example
• README.md – project overview
• Step1-Lec4, Step1-Lec5, Step2-Lec1, Step2-Lec2, Step3-Lec1, Step3-Lec2, Step3-Lec3 – each folder holds related problem scripts
• Each folder contains multiple .cpp files implementing a single algorithm or problem solution
• There are no configuration files (e.g., no CMakeLists.txt, no Dockerfile), so compilation is handled per-file via g++
README for additional insights
• Confirms purpose: structured DSA practice following Striver’s A2Z course
• Mentions usage: compile with g++ -std=c++17 filename.cpp -o output and run
Main components
a. Code Modules (Lecture folders + Patterns.cpp)
b. Build Tool (g++ compiler)
c. Developer Interface (Terminal/CLI)
d. Execution Environment (OS, C++ runtime / STL)
e. Output (Console/Stdout)
Relationships and interactions
• Developer invokes g++ on a selected .cpp file in a folder
• g++ reads the source file and linked STL headers, emits an executable
• Developer runs the executable; it interacts with C++ runtime and prints to console
• The repository on GitHub is the source control endpoint; code is pushed/pulled via git
Architectural patterns & design principles
• Modular organization by topic/lecture
• Single-responsibility for each .cpp (one algorithm/problem per file)
• No shared library or service – flat compilation model
Final advice
• Build-run cycle end to end
• Do not overthink: the architecture is essentially “developer → build → run” with code organized by topic