I think the point that he is making is that the additional friction is a good thing and necessary in this case because it's an open source project. It's too easy to do drive-by PRs that don't actually provide value and just eat up review cycles. The issue requirement simply ensures that the requester actually is invested and cares enough about this to get approval before starting work on it.
I can see why that doesn't sound great particularly on a team where everyone knows each other and is working together but it totally makes sense for me if I were maintaining a project that was large enough to get a lot of low-effort PRs coming into it.
We are a fast-growing, mission-driven fintech company that provides quality financial services for people whose needs go unmet by traditional institutions. We serve people with complex needs and those who care for them, and it is an honor to wake up in the morning knowing that we have a profound impact on our customers’ lives.
In this role, you’ll use your software development skills to make this thoughtful fintech work happen! While you’ll spend most of your time hands-on coding in our Rails/React stack, you’ll also be taking the time to understand the architecture, mentor and learn from those around you to create sustainable software.
What makes it great to work with us:
- Genuinely kind and caring people
- Making life better for the people helped least in the world
- High autonomy and few required meetings
- Start-up life without the ridiculous hours and with good compensation
I can see why that doesn't sound great particularly on a team where everyone knows each other and is working together but it totally makes sense for me if I were maintaining a project that was large enough to get a lot of low-effort PRs coming into it.