Pearl Init

Author: ScorchedPearl

readme.md

@@ -0,0 +1,172 @@
+# CP Daily Challenge
+
+Welcome to **CP Daily Challenge** — a structured daily practice repository for **competitive programming**.  
+This repo is dedicated to **consistency, discipline, and long-term CP mastery** through **daily problem solving**.
+
+Whether you're preparing for:
+- Coding Contests  
+- Technical Interviews  
+- GATE / ICPC / Codeforces / LeetCode  
+- Long-term CP growth  
+
+This repository is your **daily grind companion**.
+
+---
+
+## Purpose of This Repository
+
+The goal of **CP Daily Challenge** is to:
+
+- Maintain **daily coding consistency**
+- Improve **problem-solving speed & accuracy**
+- Track **long-term competitive programming growth**
+- Cover **all CP topics gradually**
+- Build a **strong public CP practice log**
+- Encourage **habit-based learning**
+
+This is not about quick results — this is about **discipline and mastery**.
+
+---
+
+## Daily Challenge Format
+
+Each day includes:
+
+- 1–3 Problems  
+- Problem statements / links  
+- Clean solutions  
+- Explanation / Thought process  
+- Time & Space Complexity  
+- Mistakes & Learnings (optional but encouraged)  
+
+---
+
+## Repository Structure
+
+/day-001
+/day-002
+/day-003
+...
+
+
+Each day may contain:
+
+- `problem.md` → Problem statement or link
+- `solution.cpp` / `solution.py` → Implementation
+- `notes.md` → Learnings, optimizations, mistakes
+
+Folder naming is strictly sequential.
+
+---
+
+## Topics Covered
+
+Over time, this challenge will cover:
+
+- Arrays & Strings  
+- Searching & Sorting  
+- Mathematics  
+- Recursion & Backtracking  
+- Dynamic Programming  
+- Greedy Algorithms  
+- Graph Theory  
+- Trees & Binary Trees  
+- Bit Manipulation  
+- Segment Trees & Fenwick Trees  
+- Advanced CP Topics  
+
+---
+
+## How to Participate
+
+Anyone can participate.
+
+### Steps to Join
+
+1. **Fork this repository**
+2. **Create a new branch with your name**
+
+git checkout -b your-name
+
+3. Solve today’s challenge
+4. Add your solution in the respective `day-XXX` folder
+5. Commit and push your work
+6. Create a **Pull Request (PR)**
+
+Your contributions will help build a massive CP practice archive.
+
+---
+
+## Contribution Rules
+
+- Only **original solutions**
+- Code must be **clean & readable**
+- Add **explanations wherever possible**
+- Mention **time & space complexity**
+- No copy-paste without learning purpose
+- Avoid spoiler dumps without logic
+
+Low-effort PRs will not be merged.
+
+---
+
+## Discipline Rules (Optional but Powerful)
+
+- Solve **at least one problem every day**
+- Never skip **two consecutive days**
+- Maintain a **daily streak**
+- Focus more on **thinking than codes**
+
+Consistency beats talent in CP.
+
+---
+
+## Tracking Progress
+
+You can track:
+
+- Total days completed
+- Topics mastered
+- Mistakes reduced
+- Speed improved
+- Interview readiness
+
+This repo becomes your **public CP portfolio**.
+
+---
+
+## Long-Term Vision
+
+- 100-day CP Streak
+- Interview-ready problem bank
+- Topic-wise filtered difficulty
+- Public CP journey for motivation
+- Recruiter-visible skill proof
+
+---
+
+## Support This Project
+
+If you find this useful:
+
+- ⭐ Star this repo
+- Fork it
+- Share it with your CP friends
+- Stay consistent
+
+---
+
+## 📬 Contact & Suggestions
+
+For:
+
+- Issues
+- Improvement ideas
+- New challenge formats
+- Collaboration
+
+Open an **Issue** or submit a **Pull Request**.
+
+---
+
+### One Day. One Problem. One Step Closer to Mastery.