loading...

Best Github Repositories a programmer should check out

srinivaskandukuri profile image ~#S*K#~ ・Updated on ・2 min read
  1. Some useful websites for programmers : Best websites a programmer should visit

  2. Javascript versions of classic software development algorithms
    js-algorithms

  3. Algorithms and data structures implemented in JavaScript with explanations and links to further readings
    javascript-algorithms

  4. Data Structures and Algorithms using ES6
    data-structure-and-algorithms-with-ES6

  5. :octocat: A curated awesome list of lists of interview questions. Feel free to contribute! πŸŽ“
    awesome-interview-questions

  6. A mostly reasonable collection of technical software development interview questions solved in Javascript
    interview-questions-in-javascript

  7. Some algorithms in javascript
    Algorithms-In-Javascript

  8. πŸ› Clean Code concepts adapted for JavaScript
    clean-code-javascript

  9. Collection of classic computer science paradigms, algorithms, and approaches written in JavaScript.
    computer-science-in-javascript

  10. JavaScript interview Questions
    123-Essential-JavaScript-Interview-Questions

  11. πŸ€“ Build your own (insert technology here)
    build-your-own-x

  12. Everything you need to know to get the job.
    interviews

  13. 😎 Awesome lists about all kinds of interesting topics
    awesome

  14. A Big Picture, Thesaurus, and Taxonomy of Modern JavaScript Web Development
    spellbook-of-modern-webdev

  15. Roadmap to becoming a web developer in 2019
    Roadmap

Discussion

pic
Editor guide
Collapse
ncomet profile image
Nicolas Comet

"Best Github Repositories a JavaScript programmer should fork check out"

There, fixed it.

Collapse
srinivaskandukuri profile image
~#S*K#~ Author

We developers have a habbit, if really like something we go through regularly, the best to bookmark is fork the repo.
That's how I do most of the time

Collapse
ncomet profile image
Nicolas Comet

Yes you are right, we do have our habits. However, I like to think they are as they should be, personal.

If I'm interested in a repo on github, I'll bookmark it by liking it. If I want to learn how the code of a complex library/framework works, I'll git clone it. If I want to contribute, I'll fork it.

That's my personal tastes though ;)

Thread Thread
tanuj101 profile image
Tanuj Nagpal

And that is the right way @S*K .

Thread Thread
srinivaskandukuri profile image
~#S*K#~ Author

Updated, thanks guys.

Collapse
tanuj101 profile image
Tanuj Nagpal

"should" fork?
"should"?!
But? But why? should??!!
Most of the repos you mentioned are just to read. Fork is not like a "like". If you kinda bookmark or like leave a star. Not fork it.

Collapse
bradtaniguchi profile image
Brad

I love a good lists of lists!

Collapse
yysofiyan profile image
Yanyan Sofiyan

thanks for share

Collapse
wintercounter profile image
Victor Vincent

Why you would want to fork anything without contributing to it? It's literally just junk and waste of resource.

Collapse
dejobratic profile image
Dejan Bratic

You can contribute even if you fork a repo. You can find more info here: help.github.com/en/github/getting-...

Collapse
wintercounter profile image
Victor Vincent

I think you misunderstanding what I wrote.