The ability to understand a codebase is really helpful when one is trying to make tweaks/develop the underlying code. Ideally, repos have good documentation to guide the interested developer but for the most part, this may not necessarily exist.
Therefore, given a GitHub repo, what's a good strategy to understand (in broad strokes) the structure of the code?
For further actions, you may consider blocking this person and/or reporting abuse
Recently Heroku shut down free Heroku Dynos, free Heroku Postgres, and free Heroku Data for Redis on November 28th, 2022. So Meshv Patel put together some free alternatives in this classic DEV post.
Wesley Miranda -
Bhavin Moradiya -
Jhey Tompkins -
Heather Parker -
Once suspended, kvgc will not be able to comment or publish posts until their suspension is removed.
Once unsuspended, kvgc will be able to comment and publish posts again.
Once unpublished, all posts by kvgc will become hidden and only accessible to themselves.
If kvgc is not suspended, they can still re-publish their posts from their dashboard.
Once unpublished, this post will become invisible to the public and only accessible to kvgc.
They can still re-publish the post if they are not suspended.
Thanks for keeping DEV Community safe. Here is what you can do to flag kvgc:
Unflagging kvgc will restore default visibility to their posts.
Top comments (1)
Start with the folder structure. If it's bad it's probably not worth understanding ... :/