How echobash/30_days_of_data_structure works
Project type and purpose
• This is a monolithic, language-centric code library for learning and practicing Python algorithms, data structures, OOP, and design patterns.
• There is no running front end or external service—everything executes in a local Python runtime.
File structure
• Top-level “components” are your category folders:
– LLD (Low-Level Design): design patterns and OOP examples
– Maths, Patterns, Sorting, Array, BinarySearch, Graph, Hashing, Set, String, Tree: algorithm exercises
– Other Concepts (Loops, Recursion, Python Profiling)
• README.md describes each category and how to run code.
• No external databases or message queues; minimal dependencies.
Main components
a. Git Repository (source control)
b. Local Developer Machine / IDE (where code is cloned, edited, executed)
c. Python Runtime Environment (interpreter, virtualenv)
d. Code Modules (each category as a sub-component)
– LLD
– Algorithms: Maths, Patterns, Sorting, Array, BinarySearch, Graph, Hashing, Set, String, Tree
– Utilities: Loops, Recursion, Python Profiling
e. README / Documentation
Relationships and interactions
• The Developer clones/pulls from Git Repository.
• The Python Runtime imports files from each code module.
• The Developer runs a specific script via python <module>/<file>.py.
• README guides the Developer to locate and execute examples.
Architectural patterns or design principles
• Logical separation by topic—the “package” pattern (monolith subdivided into feature packages).
• Algorithm folders have naming conventions (brute force vs optimized variants).
Final checklist
• Clear, distinct labels on every component
• Call out the README as the entry point for usage guidance
• Sub-structure in LLD (e.g., “Design Patterns” vs “Oops/interface_and_abc”)