It was great to read about your in-depth process on this, Raviraj. Only some of it applies for me on the frontend side, but I was able to do the translations and make it work.
Thanks as well for the shout-out on my recent article 🙇♂️
One effective way that I found was by assigning myself to resolve as many bugs as possible. That made me go through different pieces of code many times and that repetition helped me memorize the code.
It was great to read about your in-depth process on this, Raviraj. Only some of it applies for me on the frontend side, but I was able to do the translations and make it work.
Thanks as well for the shout-out on my recent article 🙇♂️
Glad it worked out. I kinda knew I may make it more backend specific but the rules should be transferable.
One effective way that I found was by assigning myself to resolve as many bugs as possible. That made me go through different pieces of code many times and that repetition helped me memorize the code.
Feeding the codebase into LLMs can be another good option in future as models become really powerful. Eg. - https://www.linkedin.com/posts/debarghyadas_i-saw-this-trending-github-repo-today-called-activity-7216633276919087106-MwCb
Maybe, once they get good it can help with the early explorations. Though the pain of going through the whole thing helps me remember more I think.
True, no substitute for that and also fixing bugs :)