Hacker News new | ask | show | jobs
by metravod 64 days ago
These are essentially Pigouvian taxes; frankly, I think they'll only serve to create a barrier for junior developers. I'm a supporter of stricter documentation requirements—ADRs, tests, and so on. And of course, the institution of reputation—contribution to the community will become increasingly important.
1 comments

> I think they'll only serve to create a barrier for junior developers.

I proposed some ideas how to lower entry barriers: https://e10v.me/matching-markets-congestion/#entry-barriers-...

> I'm a supporter of stricter documentation requirements—ADRs, tests, and so on.

But what would you do if there were a lot of incoming PRs and your capacity was not enough to review if they conform to requirements?

I see more comments from projects' members that they just start banning people or closing incoming PRs. I'm not sure that helps junior developers.

Yes, these are sound ideas, but such a system needs to undergo a number of balancing iterations.

As for the huge number of PRs, it's an arms race. The slew of generated PRs needs to be responded to with similar automated tools—and I'm not just talking about generation, but also about deterministic checks, and with them, raising the requirements for PR formatting.

Plus, you can create a funnel of checks—from new community members to more experienced ones—which will give them the opportunity to prove themselves and build their reputation.