Wouldn't it be nice if we could share our code on a repository and get practice with github while we're at it? 🤩
The purpose of the algo study group is to become an algo ninja, but also to create the habit of trying and doing algorithms so that we get 1% better each time and eventually get better and better to be 1000% better.
On your own we should read up on what this is all about. Please add resources to the resources folder through a pull request or be a contributor and merge yours info with what's there.
The topics are sourced from the following:
- grokkings algorithms
- cracking the coding interview
- article by Esco Obong with good overviewo of what you need to know
- MIT Course using the titles of the videos. Shoutout to Victor for recommending this course
I organized it in this notion doc and eventually that table will be what is here, except we share our code. Shoutout to kaitlin and her awesome notion notebooks that inspired me.
Meet to go over problems we tried and share our code here before or after the call. Info on meeting will be on slack. Share your code even if you can't come it will motivate us all!
For the most part we are going through the immersive and this may be an afterthought, but also a muscle 💪🏻 we've got to flex for interviews
| Week | Folder | Add Runkit here | Level | Link |
|---|---|---|---|---|
| 5/23 | Basic Data Structures | Arrays | Easy | https://leetcode.com/problems/contains-duplicate/ |
Will add the problem of the week here each week.
please add resources to the markdown file in the resources folder
- Step 1: make a branch
- Step 2: clone that branch to your computer
- Step 3: make changes
- Step 4: contribute those changes through a pull request. On a branch you can also merge it yourself if you have the permissions.
On a branch you can work on the document while others are working too and then pull and merge when you are done.
- What happens when the remote main is updated and your local code wasn't updated?
git pullwhat is on the remote repositorygit mergewill show you all the changes that you choose to stay or go. quick merge tutorial here- then add, commit and push per usual
Forks are best used: when the intent of the 'split' is to create a logically independent project, which may never reunite with its parent. Branches are best used: when they are created as temporary places to work through a feature, with the intent to merge the branch with the origin
Shoutout to Victor for clarifying this.
testing testing how are you adding this as well from github