Why I Started Contributing to Open Source (and What Happened in the First Few Months)

Description and use

A Java backend developer started contributing to open source to gain external review. He faced challenges finding unassigned issues and navigating large codebases, but learned to communicate with maintainers and make small, review‑friendly changes. His PRs were merged in Zalando Logbook, Adyen Java API Library, and Picnic error‑prone‑support, enhancing his skills.

Problem

Private codebase at work limited external review and learning opportunities.

Outcome

Merged PRs in Zalando Logbook, Adyen Java API Library, and Picnic error‑prone‑support; learned review process and improved coding skills.

Workflow

• 1. Picked a few Java projects to contribute to.
• 2. Searched for issues not already assigned.
• 3. Read the codebase to understand context.
• 4. Communicated with maintainers before coding.
• 5. Made small, focused changes and submitted PRs.
• 6. Actively responded to review comments.

Evidence

I wanted a place where I could write real code, get it reviewed by strangers, and prove to myself that I could work on a codebase I did not write.

Source

The most useful thing I learned early: talk to the maintainer before writing any code. It saves time for both sides, and it tells you quickly if the issue is worth your effort.

Source

Till now I have had PRs merged in: Zalando Logbook, Adyen Java API Library, Picnic error‑prone‑support.

Source