Los Angeles Meta Developer Circle - 100 Days Algorithms
The goal is to create a community to motivate each other on a daily basis to stay focus and to improve your algorithm/data structure skills that represent the foundation of any programming language.
For 100 days, i will push 1 exercise every day The next day i will push the answer for the previous day and 1 new exercise
- Choose a programming language
- Review basic of your favorite programming language
- Clone repository to your local machine
- Create a branch with your name
- Every day, commit your code of the day, for example day 1 will have commig
d01
- Push your code to your branch
- share your daily progress on the developer circle page
- make it a personal commitment
- don't look at answer on internet
- don't use any IDE, use a command line if possible
- push your code even if you didn't finish your exercise
- don't push to master, only on your branch
- Choose a Programming Language and Learn The Fundamentals of it
- Review basic data structure
- Review time and space complexity
- you will be overwhelmed with so many questions and you will face a lot of difficulty in solving the problems. It’s okay if you take more time in solving the questions but don’t be discouraged.
- If you’re a beginner then try to commit at least 4-6 hours every day
- If you’re an experienced try to commit for 2-3 hours every day
- Try to solve the problems on your own first even if it takes a couple of more hours. After spending many hours if you don’t get the solution then you can stretch yourself for a few days or take the hints. As you will progress you will see improvement in yourself and also you will take less time in solving the questions.
- https://git-scm.com/book/en/v2/Git-Basics-Getting-a-Git-Repository
- https://www.youtube.com/watch?v=RB5nWzdl-b8
- https://www.java67.com/2015/09/top-10-algorithm-books-every-programmer-read-learn.html?m=1
- https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository