What I learned from a small open source PR

A small PR can show real engineering skill when it is focused and easy for maintainers to review.

Before I tried open source, I thought contribution means a big feature. Now I think a small bug fix can be better for learning.

A good PR has a small story. Find the issue, understand why it happens, make a focused change, and add a fixture or test if possible.

The hard part is not only writing code. The hard part is reading the project style and respecting how maintainers think.

This changed how I see engineering. Good code is not loud. It is clear, reviewable, and it reduces work for other people.