midnightlightning

@midnightlightning@beehaw.org

This is a remote user, information on this page may be incomplete. View at Source ↗

⁨Comment⁩ on ⁨How do you wrap your head around large established software projects in order to contribute to them?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:
It seems like you might be describing two different beasts, which could be part of your difficulty:

A codebase that has “dozens and dozens of classes and header files” sounds like a back-end project (written in C or similar), where the end product is an EXE or server app. A codebase where you’d help by updating “placement of a button” is a front-end project (written in HTML or JavaScript), where the output is HTML.

If you’ve cut your teeth contributing to front-end projects, you’ll likely feel more at home contributing to projects where the output is a website. There is a vast difference between working on a project that uses NextJS and contributing to the NextJS engine codebase itself. Finding a project that is using a library you know would be likely much easier to contribute to than contributing to the library itself.