I wish to keep only algorithm implementations / tutorials here so that I can find them easily. coding-creed-origins is bloated, and I can't find things in there.
To my future self: Let's make some rules:
- For sample problems, file names should be
<platformName>-<problemNumber>-<problemTitle>.<extension>For example,leetCode-127-word-ladder.cpp,codeForces-1639A-treasure-hunt.cpp, etc. - Since file name is self explainatory, let's create commit messages based on problem categories / tags. For example, a sample commit message
:rocket: `hard(Lt-007):` #tags graph bfs string hash_set microsoft(4) google(3)I mean, I'm not working on a project, so I don't need a title, followed by bullet points explaining what was the problem, what the feature should be, what I did to implement it, etc in a commit message. 3. Keep it simple stupid! (KISS)
- LeetCode-128-longest-consecutive-sequence.md
- LeetCode-456-132-pattern.md
- leetCode-740-delete-and-earn.md
- leetCode-82-remove-duplicates-from-sorted-list-ii.md
- leetCode-847-shortest-path-visiting-all-nodes.md
- leetCode-895-maximum-frequency-stack.md
Hard category - Sqrt decomposition
- cp-algorithms This is my new favourite website! Study this thoroughly
- RodneyShag/LeetCode_solutions
- MathBugs an interesting website focusing on math problems
- kth-competitive-programming/kactl A 25 page pdf sample to be used in ICPC contests (Reminder to myself: take inspiration from here, and build your own version)
(Yeah, I watch others' solutions a lot because if it takes more than 20 minutes, you probably can't figure it out. So one should study related topics, see some example solutions etc. )
Follow the instructions precisely: link
Once installed, start docker using:
sudo systemctl start dockerAnd stop docker using:
sudo systemctl stop docker # gives a warning: Warning: Stopping docker.service, but it can still be activated by: docker.socket
sudo systemctl stop docker.socket