Skip to content

Rules In our version, of 100DaysOfCode, you need to do anything that helps you enhance your tech stack i.e. competitive coding, try learning a new language, read technical articles/ books, make open source contributions, add features to a personal project, etc. It's okay if you are not able to submit a pull request someday, you can resume it the…

License

Notifications You must be signed in to change notification settings

HarshArya-2107/Codeshow-100days_of_code

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Codeshow-100days_of_code

100DaysOfCode is a challenge/community, where you publicly commit to code for 1 hour for the next 100 days.

Rules

-In our version, of 100DaysOfCode, you need to do anything that helps you enhance your tech stack i.e. competitive coding, try learning a new language, read technical articles/ books, make open source contributions, add features to a personal project, etc.

-It's okay if you are not able to submit a pull request someday, you can resume it the next day, you will still be in the competition. Remember, life is not a sprint but a marathon, so is the path to learning and growning.

-Keep defining your short term goals (measurable) and strive hard to achieve them. (Eg. Getting better at competitive coding is not a measurable goal but achiving 2000 rating in Codechef is measurable.

-Update everyday progress and submit a pull request.

-(Optional) Follow 100DaysOfCode Twitter Bot that retweets the tweets that contain the #100DaysOfCode hashtag and timely tweet your progress with #100DaysOfCode hashtag.

-Try to add detailed description of what you did, add corresponding links, if you solve questions, you can add your codes in the same folder and provid a link in the README (not for active contests).

-We start the marathon on November 1, 2020. feel free to add your goals beforehand (they can also be added later).

Benefits

-Coding will become a daily habit for you.

-Every day that you consistently code, you’ll build momentum. That momentum will make it easier for you to learn more advanced topics.

-The projects that you’ll build will be small in scope, so by the time you finish, you’ll have completed several of them — and gained a wide range of experience.

-Your GitHub profile will look extremely active. And yes, hiring managers and recruiters do look at these.

-You’ll get more comfortable contributing in open soruce. It will become a natural, ordinary thing to do.

-You’ll have a pretty good reason to stop procrastinating and start coding every day.

-Increase your efficiency by checking your daily progress and analysing it.

-Compare your progress with others and surpass your limits in learning each day.

Recognition

-You will be provided with certificates on successful completiton of 100DaysOfCode.

-A big surprise for the overall top performers in 100DaysOfCode.

Pre-requisites

Markdown: -You need to update your README in Markdown (a lightweight markup language with plain text formatting syntax).

No need to learn it you can always refer to the guide or use an online markdown editor.

Basic git:

-Basic knowledge of git and its workflow is a must. If you are not comfortable, feel free to ask for help.

How to participate

-Fork the repository,and clone it to your local machine

-In your cloned repo, make a folder by the name of your github account.

-In your folder, make a file with the name README.md

-We have also provided a template which you can follow to set up README.md

-Update the progress in your README according to date and submit a pull request.

-If you need more clarification, feel free to reach us at Whatsapp.

About

Rules In our version, of 100DaysOfCode, you need to do anything that helps you enhance your tech stack i.e. competitive coding, try learning a new language, read technical articles/ books, make open source contributions, add features to a personal project, etc. It's okay if you are not able to submit a pull request someday, you can resume it the…

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Jupyter Notebook 77.8%
  • Java 12.9%
  • C++ 8.4%
  • Other 0.9%