Having worked with Git and GitHub for a while now, the process of forking, cloning, branching, and submitting pull requests has become second nature to me. That said, the most exciting part of the workflow for me every time is the moment just before submitting a PR, when I discover something worth fixing. Whether it's a typo in documentation, an inconsistency in the reference, or even an actual bug in the code, that discovery feels like a small puzzle to solve, and the satisfaction of fixing it makes the whole process worthwhile.

I do remember a humbling early habit: I used to forget to switch to a development branch and would code directly on main, only realizing the problem right before committing when conflicts would surface. After making that mistake a couple of times, it finally stuck. Now I genuinely appreciate the discipline of branching. It's not just a rule to follow, but a way to track incremental progress across different aspects of a project, preserve a clean history, and make rollbacks painless if something goes wrong.

On the readings side, the Open Source Ethos piece gave me a broader appreciation for what open source actually represents — not just freely available code, but a philosophy of transparency, shared ownership, and collective progress. A friend and I are planning a small open source project for the NYU Shanghai community, and since neither of us has much experience running something like that, the Building Welcoming Communities guide on opensource.guide was especially eye-opening. The idea that a community's culture is just as important as its codebase — that people contribute more when they feel genuinely welcomed and heard — is something I want to be intentional about from the very start of our project.