Coding is not the problem; the bottleneck is in the review process.
Writing code? Everyone wants to try. But only a few are truly willing to do reviews.
An open-source project maintainer once told me an interesting phenomenon — even just a PR fixing a typo can take up valuable review time. This seemingly trivial change consumes a significant amount of focus and effort behind the scenes. This issue is especially prominent in DeFi projects, smart contract libraries, and on-chain infrastructure maintenance. How to balance contribution quality and review efficiency has become a core challenge in the open-source ecosystem.
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
11 Likes
Reward
11
7
Repost
Share
Comment
0/400
OffchainOracle
· 11h ago
Really, reviewing this work is indeed exhausting. A bunch of PRs with spelling errors pile up, and reviewers have to go through them one by one, so annoying.
Reviewing is truly the bottleneck, not writing code. Especially in DeFi, it's particularly difficult; a small oversight can cause issues.
Honestly, there are many who want to contribute, but few are willing to spend time reviewing. This is probably the current state of the open-source ecosystem.
Smart contract review is truly challenging; missing a detail can lead to millions in losses. Maintainers really can't keep up.
There are only a few, each project lacks reviewers. Wasting time on trivial changes—who can stand that?
View OriginalReply0
rug_connoisseur
· 11h ago
Really, censorship is such a hassle, a bunch of minor tweaks take half a day...
View OriginalReply0
BetterLuckyThanSmart
· 11h ago
Exactly right, that's really how the review process works. A bunch of people rush in to submit PRs, and the reviewers are exhausted, yet they still go through each one, catching typos one by one.
View OriginalReply0
BlockDetective
· 11h ago
Really? Reviewing is truly much more exhausting than coding, especially in DeFi... Even a typo means going through the entire logic from the beginning, I can't handle it.
View OriginalReply0
NotAFinancialAdvice
· 11h ago
That's why many projects end up abandoned, with too many PRs piling up and too few reviewers available.
View OriginalReply0
rugdoc.eth
· 11h ago
That's why I don't dare to casually submit PRs now; reviewers are really too exhausted.
View OriginalReply0
0xSoulless
· 11h ago
Do spelling errors in PRs also need review? Haha, this is the difference between retail investors and big players—big players just change the algorithm, while retail investors want to get on the chain even by changing a comma. The real work is all in the review process; anyone can write code, but quality control is what really matters.
Coding is not the problem; the bottleneck is in the review process.
Writing code? Everyone wants to try. But only a few are truly willing to do reviews.
An open-source project maintainer once told me an interesting phenomenon — even just a PR fixing a typo can take up valuable review time. This seemingly trivial change consumes a significant amount of focus and effort behind the scenes. This issue is especially prominent in DeFi projects, smart contract libraries, and on-chain infrastructure maintenance. How to balance contribution quality and review efficiency has become a core challenge in the open-source ecosystem.