How niteshkumartiwari/daily-competitive-programming works
Project type and purpose
• This is not a deployed or running “service” in the traditional sense, but rather a personal repository of algorithm/LeetCode practice solutions and reference materials.
• The folder structure is organized by problem category (Arrays, Graph, DP, Greedy, etc.) and also contains a “Leetcode” folder for PDF books and interview prep resources.
• There is no backend service or frontend UI—this is purely a code‐and‐docs library.
File structure
• Top‐level folders and files:
• Category folders (implicitly via file prefixes, e.g. Array1-…, Graph1-…, DP1-…, etc.).
• A “Leetcode” folder with subfolders of study materials.
• A few stray files (README.md, .gitignore, juspay.java).
• There are no build scripts, CI configs, or deployment manifests—just source files (.cpp, .java) and PDFs.
• The organization pattern is purely topical grouping of algorithm implementations.
README
• The README contains just a couple of reading links and a TO-DO—no architectural notes or tech stack details.
• Confirms the repo’s role as a personal study workspace, not a packaged product.