 Youtube channels |
 Github Repos |
 Best Coding Playgrounds |
|---|---|---|
| CppNuts | Codecademy | Leetcode |
| The Cherno | johnmcfarlane/begin(C++) | HackerRank |
| ChiliTomatoNoodle | ratansingh98/CPP-Learning | CodeChef |
| Bo Qian | sahilbansal17/Get_Better_at_CP_in_2_Months | CodeForces |
 Coding Ideas |
 Algorithms |
 Useful articles |
|---|---|---|
| CodeBlocks | Visualisze algorithms through animations | Learn CPP |
| VS Code | CP Algorithms | CF Blog : Resources for cpp |
| Follow these steps | |
|---|---|
| New Algorithm | 'Please see if the algorithm is already present' |
| What to include | "Your algorithm should be efficiently written with proper code / comments / time complexity / space complexity / link to gfg or any other documentation on top in code file" |
| Where to include | please commit your algorithm in correct folder or discuss[here](https://github.com/Lakhankumawat/LearnCPP/discussions/7)before commiting for where to include` |
| README | "Please check whether your directory has a README file , if there is then edit your algorithm name with link , otherwise create new one " how your README should look like |
| Follow these steps | |
|---|---|
| New Problem Statement | 'Please see if the problem is present already ? If it is do not commit your own ' |
| What to include | "Your problem statement solution should be efficiently written with proper code / comments / time complexity / space complexity / link to problem statement in code file" |
| Where to include | Most of the Problem Statements are insidehereplease commit your problem solution in correct folder or discuss here before commiting for where to include |
| README | "Please check whether your directory has a README file , if there is then edit your algorithm name with link , otherwise create new one " how your README should look like |
| Additional Context | "There are three levels of problem statement" 1-Level 1 like wise 2-Level 2 & 3-Level 3 , please include your problem statement with solution in right level you prefer |
Fond of designing README this section will be helpful to you
| Follow these steps | |
|---|---|
| 🆕 New README | 'Please see if there is no README in any folder , if no ? Then please design it ' |
| 🤔 What to include | "Your README should be efficiently and clearly written / link to problem statement in README at the top" see exmaple |
| ✅ Must Contain | 1. and explain in brief about addition 2. An Image of addition i.e how it works 3. Mention the Psuedo Code 4. Time and Space Complexities 5. Advantages 6. Disadvantages |
| 🪧 Where to include | Inside the folder where programs are residing ,discuss here before commiting for where to include |
- If you find any errors or bugs then please report by creating an issue.
- If you can provide a more efficient solution or implementation of algorithm then make sure to contribute.
- If you want to implement an algorithm, data structure etc.., which is not yet there, then you can open up a PR regarding the same.
- Link to discussion forum
- Take a look at
contributing guidelinesif you're interested in helping! - Refer GitHub Flow.
Thanks goes to these wonderful people :
 SATYAM KUMAR 💻 |
 Nikita Sharma 🚧 🤔 |
 Ujjwal Bansal 💻 |
Developed with ❤️ in India 🇮🇳