This repository contains the questions, code and notes in the live sessions, which took place.
| Question | Session Code | Study References |
|---|---|---|
| 125. Check Palindrome | Solution | Leetcode, Leetcode |
| Find Anagram | Solution | GFG |
| 20. Valid Parentheses | Solution | Leetcode |
| Question | Session Code | Study References |
|---|---|---|
| Find an element in a sorted array | Solution | GFG |
| 74. Search a 2D Matrix | Solution | Leetcode |
| Search & count in 2d matrix | Solution | GFG |
| Question | Session Code | Study References |
|---|---|---|
| 70. Climbing Stairs | Solution | Leetcode |
| 2400. Number of Ways to Reach a Position After Exactly k Steps | Solution | Leetcode |
| Find the right robot/s | Solution | 1D Array, 2D Array |
Date : 11 Jan 23
| Question | Session Code | Study References |
|---|---|---|
| 848. Shifting Letters | Solution | Leetcode |
| Shifting letters 1.5 | Solution | Leetcode |
| 2381. Shifting Letters II | Solution | Prefix sum, Line sweep |
Date : 02 Jan 23
| Question | Session Code | Study References |
|---|---|---|
| Best Time to Buy and Sell Stock | Solution | Leetcode, Kadane's Algorithm |
| Best Time to Buy and Sell Stock II | Solution | Leetcode, Template |
Coming soon...
We welcome contributions to this project!
If you have an idea for a new feature or improvement, please open an issue to discuss it with the community before submitting a pull request.
Here are some guidelines to follow when contributing:
- Before making a contribution, please check the project's open issues to see if someone else is already working on something similar. If you have a new suggestion or have found a bug, please open a new issue to let us know.
- If you want to work on an existing issue or have a new idea for a feature, please comment on the issue to let us know that you are working on it. This will help to prevent duplication of effort.
- All contributions should be made via pull request. When submitting a pull request, please make sure to include a clear description of the changes you have made and why they are necessary.
- All code contributions should be accompanied by tests to ensure that the changes do not break existing functionality.
- If you are making a non-code contribution (e.g. writing documentation, creating graphics), please make sure to follow the project's style guidelines and include any necessary attribution.
1. Fork the repository.
2. Create a new branch for your changes.
3. Make your changes.
4. Push your changes to your forked repository.
5. Submit a pull request to the main repository.
- Please make sure to update the README index table above with a description of your changes after submitting your pull request.
- Do find and add the best resource you think is required to learn the question asked to you.
- Do add the session video for their questions.
- Link to the channel for above step.
GNU GENERAL PUBLIC LICENSE