github-cheat-sheet
awesome-competitive-programming
Our great sponsors
github-cheat-sheet | awesome-competitive-programming | |
---|---|---|
2 | 13 | |
45,564 | 12,138 | |
- | - | |
2.0 | 0.0 | |
8 days ago | 2 months ago | |
MIT License | Creative Commons Attribution 4.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
github-cheat-sheet
-
Question about a github book
Not aware of a book - but what you describe sounds a little like the github cheatsheet - could it be someone turned this (or the talk mentioned in the intro) into an ebook or pdf?
-
Free 500+ books and learning resources for every programmer.
GitHub Cheat Sheet - Tim Green (Markdown)
awesome-competitive-programming
-
I am SO done WitH LeEtcOdING
There are a bunch of good free resources here but they’re are a lot less digestible https://github.com/lnishan/awesome-competitive-programming
-
I would like to be able to solve Competitive Programming problems. What are the resources for this?
I suggest you look at this very comprehensive and awesome list: https://codeforces.com/blog/entry/23054
-
Resources to get started with competitive programming?
Awesome Competitive Programming
- A curated list of Competitive Programming resources
-
How to break into Hudson River Trading?
First, make a codeforces account and then refer to this resource list as you continue to solve problems.
-
Competitive Coding - A starters guide.
Start your competitive coding journey from Algorithms, Competitive Coding to Data Structure resources, everything in one awesome repository. Check it OUT!
-
What's do I need to learn for competitive programming (specifically the CCC) and whats the best way to learn it?
You need more than logic and practice. These contests are not just intelligence tests. They also test knowledge of certain algorithms, techniques, and mathematical skills. My suggestion would be to pick a problem from that contest and spend some time trying to solve it (no more than an hour or two even for harder problems). Then whether or not you solve it yourself, read an editorial or someone else's solution. Make a note of any concepts you're not familiar with, and read up on them. You should be able to find everything you need online, but https://github.com/lnishan/awesome-competitive-programming has other sources including books. Then solve the problem again and make sure you understand it. Once you do this enough times, you'll cover all the topics that are likely to come up in that contest.
-
Good books or tutorials for competitive programming?
Take a look at the Awesome Competitive Programming list on GitHub. All the standard references are there.
- How long does it take to be able to churn out solutions to Google kickstart problems within time limit?
What are some alternatives?
devdocs - API Documentation Browser
awesome-for-beginners - A list of awesome beginners-friendly projects.
book - The Rust Programming Language
awesome-nodejs - :zap: Delightful Node.js packages and resources
CppCoreGuidelines - The C++ Core Guidelines are a set of tried-and-true guidelines, rules, and best practices about coding in C++
javascript-algorithms - 📝 Algorithms and data structures implemented in JavaScript with explanations and links to further readings
awesome-remote-job - A curated list of awesome remote jobs and resources. Inspired by https://github.com/vinta/awesome-python
magic-trace - magic-trace collects and displays high-resolution traces of what a process is doing
awesome-eslint - A list of awesome ESLint plugins, configs, etc.
awesome-interview-questions - :octocat: A curated awesome list of lists of interview questions. Feel free to contribute! :mortar_board:
git-internals-pdf - PDF on Git Internals
Crafting Interpreters - Repository for the book "Crafting Interpreters"