For B4tman. I don't quite understand why you got down-voted, besides maybe because your question has two opposing thoughts, which may or may not be self evident

For B4tman. I don't quite understand why you got down-voted, besides maybe because your question has two opposing thoughts, which may or may not be self evident to your self. Let's break your sentence down. "How do you start a new/big project? Lets say I want to read a codebase on github which is written in js. How doI go through it, given that I don’t know much js yet?" The first part about how to start a new big project has nothing to do with reading a codebase. And the part not knowing much js yet means you shouldn't be starting a big project. You could, if you wanted to. Heck, I've done it but nothing good has come out of it besides learning that, baby steps are sane steps. So, we have two questions. 1- How to start a big project? (whatever big may mean to you). 2- How to read a codebase. Reading a codebase will help you understand project structure. It will also help you, that is, if you find a line of code you don't understand, break it down, research what it does and continue reading, improve your coding abilities. In short, how everything ties together. That practice will help you understand how to start a new project. But the first step you ought to take is, if you are going to go down this road, is to learn how to ask questions: https://stackoverflow.com/help/how-to-ask https://stackoverflow.com/help/how-to-ask http://www.catb.org/esr/faqs/smart-questions.html http://www.catb.org/esr/faqs/smart-questions.html