Introduction

It's very overwhelming for anyone new to get started and write code from the get-go. There are a lot of amazing resources out there to learn and grow. But one of the major problems newcomers face is the problem of analysis paralysis.

As there is an uncountable amount of courses and tutorials. It gets overwhelming very quickly and people get stuck in "tutorial hell". So this is a streamlined list of resources, that you can dive in blind and start writing code as soon as possible.

By no means this list is a catch-all end-all. But if you don't know what to do, this is a really good starting point

CS50

CS50 is an introductory computer science course by Harvard and Yale University. The course is run on-campus and online. The name is a play on "101"s being the introductory courses of their respective subjects. This signifies the inclusive nature of the course, one popular metric the instructor likes to quote is that around 70% people taking CS50 have no prior experience in writing code.

The first week talks about the representation of numbers in binary, and the general thought process of iterative thinking i.e. giving the student a good experience of "thinking like a computer"
Subsequent weeks, talk about basic algorithms and pointers.
And continue to various topics, such as web servers, etc.

It is a great resource to get started in computer science. It provides a basic intuition of computer science, which goes a long way.

Whether you're interested in web development or systems programming, this is one of the best ways to get started.

https://cs50.harvard.edu/x/2020/

Don't Rush

This section is taken from a popular blog by Peter Norvig (Director of Research @ Google)

Teach Yourself Programming in Ten Years

Researchers (Bloom (1985), Bryan & Harter (1899), Hayes (1989), Simmon & Chase (1973)) have shown it takes about ten years to develop expertise in any of a wide variety of areas, including chess playing, music composition, telegraph operation, painting, piano playing, swimming, tennis, and research in neuropsychology and topology.

The key is deliberative practice: not just doing it again and again, but challenging yourself with a task that is just beyond your current ability, trying it, analyzing your performance while and after doing it, and correcting any mistakes. Then repeat. And repeat again. There appear to be no real shortcuts: even Mozart, who was a musical prodigy at age 4, took 13 more years before he began to produce world-class music.

So You Want to be a Programmer

Get interested in programming, and do some because it is fun. Make sure that it keeps being enough fun so that you will be willing to put in your ten years/10,000 hours.
Program. The best kind of learning is learning by doing. To put it more technically, "the maximal level of performance for individuals in a given domain is not attained automatically as a function of extended experience, but the level of performance can be increased even by highly experienced individuals as a result of deliberate efforts to improve." (p. 366) and "the most effective learning requires a well-defined task with an appropriate difficulty level for the particular individual, informative feedback, and opportunities for repetition and corrections of errors." (p. 20-21) The book "Cognition in Practice: Mind, Mathematics, and Culture in Everyday Life" is an interesting reference for this viewpoint.
Talk with other programmers; read other programs. This is more important than any book or training course.
If you want, put in four years at a college (or more at a graduate school). This will give you access to some jobs that require credentials, and it will give you a deeper understanding of the field, but if you don't enjoy school, you can (with some dedication) get similar experience on your own or on the job. In any case, book learning alone won't be enough. "Computer science education cannot make anybody an expert programmer any more than studying brushes and pigment can make somebody an expert painter" says Eric Raymond, author of The New Hacker's Dictionary.
Work on projects with other programmers. Be the best programmer on some projects; be the worst on some others. When you're the best, you get to test your abilities to lead a project, and to inspire others with your vision. When you're the worst, you learn what the masters do, and you learn what they don't like to do (because they make you do it for them).
Work on projects after other programmers. Understand a program written by someone else. See what it takes to understand and fix it when the original programmers are not around. Think about how to design your programs to make it easier for those who will maintain them after you.
Learn at least a half dozen programming languages. Include one language that emphasizes class abstractions (like Java or C++), one that emphasizes functional abstraction (like Lisp or ML or Haskell), one that supports syntactic abstraction (like Lisp), one that supports declarative specifications (like Prolog or C++ templates), and one that emphasizes parallelism (like Clojure or Go).
Remember that there is a "computer" in "computer science". Know how long it takes your computer to execute an instruction, fetch a word from memory (with and without a cache miss), read consecutive words from disk, and seek to a new location on disk.

Fred Brooks, in his essay No Silver Bullet identified a three-part plan for finding great software designers:

Systematically identify top designers as early as possible.
Assign a career mentor to be responsible for the development of the prospect and carefully keep a career file.
Provide opportunities for growing designers to interact and stimulate each other.

This assumes that some people already have the qualities necessary for being a great designer; the job is to properly coax them along. Alan Perlis put it more succinctly: "Everyone can be taught to sculpt: Michelangelo would have had to be taught how not to. So it is with the great programmers". Perlis is saying that the greats have some internal quality that transcends their training. But where does the quality come from? Is it innate? Or do they develop it through diligence? As Auguste Gusteau (the fictional chef in Ratatouille) puts it, "anyone can cook, but only the fearless can be great." We think of it more as willingness to devote a large portion of one's life to deliberative practice. But maybe fearless is a way to summarize that. Or, as Gusteau's critic, Anton Ego, says: "Not everyone can become a great artist, but a great artist can come from anywhere."

So go ahead and buy that Java/Ruby/Javascript/PHP book; you'll probably get some use out of it. But you won't change your life, or your real overall expertise as a programmer in 24 hours or 21 days. How about working hard to continually improve over 24 months? Well, now you're starting to get somewhere...

Open Source

Good First Issues

Languages

Starting with some language

Showcasing why any language works and recommending sticking to it

How to decide

Several people have asked what programming language they should learn first. There is no one answer, but consider these points:

Use your friends. When asked "what operating system should I use, Windows, Linux, or Mac?", the answer is "use whatever your friends use." The advantage you get from learning from your friends will offset any intrinsic difference between OS, or between programming languages. Also consider your future friends: the community of programmers that you will be a part of if you continue. Does your chosen language have a large growing community or a small dying one? Are there books, web sites, and online forums to get answers from? Do you like the people in those forums?
Keep it simple. Programming languages such as C++ and Java are designed for professional development by large teams of experienced programmers who are concerned about the run-time efficiency of their code. As a result, these languages have complicated parts designed for these circumstances. You're concerned with learning to program. You don't need that complication. You want a language that was designed to be easy to learn and remember by a single new programmer.
Play. Which way would you rather learn to play the piano: the normal, interactive way, in which you hear each note as soon as you hit a key, or "batch" mode, in which you only hear the notes after you finish a whole song? Clearly, interactive mode makes learning easier for the piano, and also for programming. Insist on a language with an interactive mode and use it.

The important thing is that you choose and get started.

This section is taken from a popular blog by Peter Norvig (Director of Research @ Google)

JavaScript

Go

Rust

Rusty (╯°□°)╯︵ ┻━┻

Elixir

Elixir is used to build highly scalable, fault-tolerant applications. It's a functional language, and leverages the BEAM VM(Virtual Machine), which erlang and many other languages use.

Watch this(The Soul of Erlang and Elixir • Sasa Juric • GOTO 2019) talk for a high level overview of Elixir(& BEAM VM).

Learning resources

The official Elixir Getting Started guide(Recommended for beginners)
Some learning resources from the official Elixir website
Hands on through Exercism
If something is not clicking, checkout this blog for indepth explanations.
(In beta) Learning elixir curriculum with projects
Official Elixir forum

Technologies

Various technologies in Computer Science

roadmap.sh

Web Dev

AI/ML

Android

DevOps

Cybersecurity

LEARN TO HACK

Hackerman

General & Tools

Books

Hands on Practice

Bug Bounty

Tools of the Trade

Add intro about why these tools are important in your programming journey

https://missing.csail.mit.edu/

Linux

Version Control

Git is the most popular version control system. It was created by Linus Torvalds(founder of Linux) to help manage the Linux kernel project.

What is a version control system?

A version control system keeps the record of the changes made by tracking the modifications made so that everything is in organized order and if something goes wrong we can get back to our previous state. It is used to keep different versions of the history of any project.

Why use git?

It is really hard to manage a project. More so the projects that include code, as changes in lines span across various files.
it's harder to understand the nature of changes by just looking at the changes in code, without re-understanding the context
easier to work with multiple people

It is recommended to learn git, as soon as you start writing code. To make a habit of good code practices

Minerva