How to quickly understanda a new codebase - using dev.to as an example!

Whenever you join a new project you ask yourself: how to quickly understand the new codebase so that I can start contributing as soon as possible? In this video I'm showing a few steps and I'm presenting how I learn a new codebase using Forem (engine used for dev.to) as an example.
Reading code is an important skill for every software engineer and by learning how to quickly get a grasp of new project you'll improve your programming skills and you'll become a better, more productive software developer.
🎥 Related videos:
* Learn faster with a pyramid of skills: • become a BETTER SOFTWA...
* How to do a good code review: • How to do Good Code Re...
* Ask these questions to write good code: • How to write good code...
🎥 Timeline:
0:00 Intro
0:30 Click around the app
1:01 Documentation matters!
1:42 2 types of dependencies
3:05 Look into the data
4:40 Start exploring, start changing
6:09 Demo time - click around the app
9:08 Demo time - read the docs
11:08 Demo time - dependencies
14:40 Demo time - into the database
17:12 Demo time - understand Forem's feed algorithm
22:04 Summary
If you enjoy this kind of content, check out my website, 🌏 notonlycode.org, where I publish more in-depth articles about software development.
As always, if you have any questions, suggestions or feedback, you can contact me:
✉️ email: [e-mail]
🐦 Twitter: @GregoryWitek

[@littlehearts7039]

An ingenious video on this topic. This is the fisrt youtube video that I am seeing with so much hands on approach and in-detail step by step exploration. Need more videos in this series sir. Thank You

[@NotOnlyCode]

Wow, thank you, I'm glad you like it!

[@ios_interview]

Hey Gregory, no updates in a while! Are you ok?

[@NotOnlyCode]

Hi, thank you for asking, that's so nice of you! I'm ok, I needed to take a break and now it's hard to get back to my weekly rhythm of creating videos. I have a few episodes waiting for editing, they should be released in a couple of weeks

[@ios_interview]

@@NotOnlyCode Why not do a live stream Q&A? It might be a nice way to start the momentum again :)