Something like LeetCode, but for code review (my experiment)
At my company we started talking about the fact that we generate more code than we can properly review, and bugs have started slipping through. I don't think we're the only ones.
Auto-reviewers don't fully solve this: some things they just don't see, and sometimes it's the opposite, they keep finding endless "improvements". So other than training the review skill itself, I don't really see a way out.
So I made my own experiment: something like LeetCode, but for code review. You open a realistic pull request, leave inline comments, give a verdict (approve / request changes), and find out whether you caught the planted bug. Some PRs have no bug at all: confidently saying "this is fine" is also a skill.
Right now there are pull requests for Python, Node and popular frontend frameworks (React, Angular). There are even a couple in COBOL. Some of the bugs I recreated from real incidents that made the news back in the day.
The project is an experiment for now and completely free: diffdojo.com
Would be interesting to hear what you think, and especially how you keep your guard up when reviewing generated code?