understanding a big codebase you have never worked.

  • MagicShel@programming.dev
    link
    fedilink
    arrow-up
    0
    ·
    1 month ago

    Look at the packages. Try to break it down into architectural layers. Understand in a broad sense what each layer adds to the one before. Rage that it wasn’t so much architected as cobbled together from pieces never designed to fit together. Decry it as total garbage and recommend total rewrite.

  • Gallardo994@sh.itjust.works
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    1 month ago

    I have two key points to understand any large codebase:

    • Start with the entry point. Check the initialization process. It will most likely tell you what other parts of the code are crucial to the application. Start digging into those parts that are mentioned in the initialization process. Rinse and repeat for their dependencies which might look important. Just read and take notes if necessary. Try to understand how the application gets its stuff running. Don’t spend too much time on a specific part, just get a broad understanding and how it all flows.
    • After the first step, you should start seeing some sort of patterns to how the software is made: repeating principles, common practices, overall architecture. This is the point when you should be confident enough to introduce changes to the software, therefore you should have a build environment which guarantees the application works. If it doesn’t, have someone in the team help you to get it running without any changes to the codebase. Don’t make changes until you have a working build environment.

    With both done, you should already be comfortable enough to start modifying the application.

    I cannot stress enough how many developers I’ve seen trying to dig into random parts of the code knowing nothing where or how it all begins, making it super-problematic to add new features. Yeah they can fix a bug or two, but the biggest issues start when they try to implement something new.

  • deegeese@sopuli.xyz
    link
    fedilink
    arrow-up
    0
    ·
    1 month ago

    Get it up and running in a dev environment and start inserting changes to see what breaks where.

    Revert and retry until you’ve learned where you’re supposed to be meddling.

    • luciole@beehaw.org
      link
      fedilink
      arrow-up
      0
      ·
      1 month ago

      Another big advantage of getting a dev environment setup is if you can get step by step debugging in place as well. You can then use that to follow the trail of a user action from the UI triggers all the way down.