The latest articles on DEV Community by λlvaro Frias (@qequ). https://dev.to/qequ https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F69888%2Ff4c99ea5-00bb-4aef-9801-cb6a526e3223.png https://dev.to/qequ en λlvaro Frias Sun, 22 Sep 2019 18:25:34 +0000 https://dev.to/qequ/approaches-and-techniques-for-learning-new-codebases-238f https://dev.to/qequ/approaches-and-techniques-for-learning-new-codebases-238f <p>Hi everyone! as the title say, I wanted to ask you what you do when you are facing a new codebase/legacy code to work to (besides looking at the docs).</p> <p><a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fthepracticaldev.s3.amazonaws.com%2Fi%2Fj2yj49tx7db2oh381mp4.jpg" class="article-body-image-wrapper"><img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fthepracticaldev.s3.amazonaws.com%2Fi%2Fj2yj49tx7db2oh381mp4.jpg" alt="Coding hard"></a></p> <p>The question arose because I want to get into the world of open source collaboration. I have forked and cloned several projects that have a lot of files, and many times no docs at all. So I get stuck in many small problems that have nothing to do with the project itself.</p> <p>Thanks all, have a nice day!</p> discuss beginners productivity help