Building problem-solving skills, one problem at a time.
My journey from solving problems → recognizing patterns → becoming a better engineer.
I'm Jeel Soni, a B.Tech student specializing in Artificial Intelligence & Machine Learning.
This repository documents my journey through:
- 🧩 Data Structures & Algorithms
- 🧠 Problem Solving
- ⚡ Algorithm Optimization
- 🎯 Technical Interview Preparation
- 💻 Software Engineering Fundamentals
This isn't just a collection of answers.
It's a record of my growth.
The goal isn't to solve everything. The goal is to become better at solving anything.
| Difficulty | Problems |
|---|---|
| 🟢 Easy | 20 |
| 🟡 Medium | 47 |
| 🔴 Hard | 6 |
| ⚪ Unknown | 0 |
| 🏆 Total | 73 |
🟢 Easy 20
🟡 Medium 47
🔴 Hard 6
⚪ Unknown 0
🏆 TOTAL 73
My approach to every problem:
🧩 Problem
│
↓
🔍 Understand It
│
↓
🐢 Brute Force
│
↓
🧠 Find Pattern
│
↓
⚡ Optimize
│
↓
💻 Implement
│
↓
🧪 Test Edge Cases
│
↓
📚 Learn
I don't want to memorize solutions.
I want to recognize patterns.
| Pattern | Status |
|---|---|
| 🔄 Two Pointers | 🔄 Learning |
| 🪟 Sliding Window | 🔄 Learning |
| 🗺️ Hash Map | 🔄 Learning |
| 🔎 Binary Search | 🔄 Learning |
| 📚 Stack | 🔄 Learning |
| 🚶 Queue | 🔄 Learning |
| 🔗 Linked List | 🔄 Learning |
| 🌳 Trees | 🔄 Learning |
| 🕸️ Graphs | 🔄 Learning |
| 💰 Greedy | 🔄 Learning |
| 🔙 Backtracking | 🔄 Learning |
| 🧠 Dynamic Programming | 🔄 Learning |
For every problem, I try to understand five things:
What exactly is the problem asking?
What is the simplest solution I can think of?
Can I recognize a known DSA pattern?
Can I improve:
Time Complexity
+
Space Complexity
I don't consider a solution complete until I think about the unusual cases.
Empty / Minimum Input
↓
Duplicates
↓
Already Sorted
↓
Reverse Sorted
↓
Single Element
↓
Boundary Values
There will be:
- ❌ Wrong Answers
- ❌ Time Limit Exceeded
- ❌ Failed Edge Cases
- ❌ Bugs
- ❌ Problems I don't understand immediately
And that's completely fine.
❌ Wrong Answer
│
↓
🔍 Understand Why
│
↓
🔧 Fix It
│
↓
🧠 Learn The Pattern
│
↓
📈 Become Better
Every wrong answer is another piece of the puzzle.
LeetCode isn't the final destination.
It's one part of a much bigger journey.
DSA
│
↓
Problem Solving
│
↓
Technical Interviews
│
↓
Software Engineering
│
↓
AI / ML Engineering
As an AI/ML student, I want to combine strong problem-solving fundamentals with machine learning and real-world engineering.
The goal is not just to build AI systems.
The goal is to become an engineer who can solve difficult problems and build reliable systems.
I don't need to solve 10 problems every day.
I need to understand one problem deeply.
1 Problem
×
365 Days
=
365 Opportunities to Improve
leetcode-solutions/
│
├── 31-next-permutation/
│ ├── README.md
│ └── solution.py
│
├── 73-set-matrix-zeroes/
│ ├── README.md
│ └── solution.py
│
├── 118-pascals-triangle/
│ ├── README.md
│ └── solution.py
│
├── scripts/
│ └── update_readme.py
│
├── .github/
│ └── workflows/
│ └── update-readme.yml
│
└── README.md
New LeetCode problems are added automatically through LeetSync.
This repository uses LeetSync + GitHub Actions.
🧑💻 Me
│
│ Solve
↓
🟠 LeetCode
│
│ LeetSync
↓
🐙 GitHub Repo
│
↓
⚙️ GitHub Actions
│
↓
🐍 update_readme.py
│
┌───────┴───────┐
↓ ↓
Count Problems Update Stats
│ │
└───────┬───────┘
↓
📊 README
This means I can focus on solving problems, while the repository handles the progress tracking.
✅ Start the journey
⬜ Build consistency
⬜ Master core DSA patterns
⬜ Solve 50 problems
⬜ Solve 100 problems
⬜ Solve 200 problems
⬜ Master advanced DSA
⬜ Become interview ready
The checklist will evolve as the journey continues.
Every commit is a small record of progress.
Every bug is a lesson.
Every optimized solution is a step forward.
Every difficult problem makes the next one a little easier.
— Jeel Soni
One problem at a time. One pattern at a time. One step at a time.