Awesome idea, just signed up to help out and review code! Is there an incentive / gamification system to reward strong reviewers so their reputation increases as they provide good feedback to companies?
Thanks! We're still early in our life cycle -- but on the roadmap is the creation of reviewer profiles (as an optional feature). This'll allow us to highlight strong reviewers, their projects, etc. Incentives and gamification are definitely there as well. We want to bonus people for doing thoughtful code review.
Launch HN: PullRequest (YC S17) – On-Demand Code Review
11–20 of 68 posts
Re: Launch HN: PullRequest (YC S17) – On-Demand Code Review
#12Earlier quoted context omitted.
Thanks! We're still early in our life cycle -- but on the roadmap is the creation of reviewer profiles (as an optional feature). This'll allow us to highlight strong reviewers, their projects, etc. Incentives and gamification are definitely there as well. We want to bonus people for doing thoughtful code review.
This is a big opportunity to create an entirely new specialized role. Could be very lucrative for people to make names for themselves.
Re: Launch HN: PullRequest (YC S17) – On-Demand Code Review
#13Re: Launch HN: PullRequest (YC S17) – On-Demand Code Review
#14Congrats on building this product, guys. This tool is very interesting for startups that have only one developer and freelancers. However, a $49/month pricing may be quite expensive for these people.
Re: Launch HN: PullRequest (YC S17) – On-Demand Code Review
#15Re: Launch HN: PullRequest (YC S17) – On-Demand Code Review
#16My workflow (which I believe is pretty standard) is:
* Write code
* Verify that tests pass locally (including stylistic tests, linting)
* Submit pull request
* Pull request triggers build and tests on Travis
* If all tests pass on Travis, code is stylistically and functionally correct
* Merge pull request
How can human reviewers improve this workflow?
Re: Launch HN: PullRequest (YC S17) – On-Demand Code Review
#17What are the benefits of reviewers over automated testing? My workflow (which I believe is pretty standard) is: * Write code * Verify that tests pass locally (including stylistic tests, linting) * Submit pull request * Pull request triggers build and tests on Travis * If all tests pass on Travis, code is stylistically and functionally correct * Merge pull request How can human reviewers improve this workflow?
Passing tests don't prove that
- tests are covering all functional criteria required
- the code doesn't add 'technical debt', i.e. structural problems that will have to be refactored/worked around in the future.
Re: Launch HN: PullRequest (YC S17) – On-Demand Code Review
#18What are the benefits of reviewers over automated testing? My workflow (which I believe is pretty standard) is: * Write code * Verify that tests pass locally (including stylistic tests, linting) * Submit pull request * Pull request triggers build and tests on Travis * If all tests pass on Travis, code is stylistically and functionally correct * Merge pull request How can human reviewers improve this workflow?
A PR is about showing the rest of the team the changes so more than one person knows how stuff work and what's going on in the code base. And for the rest of the team to give feedback on stuff like how the feature was architected, not to nitpick on indenting.
Re: Launch HN: PullRequest (YC S17) – On-Demand Code Review
#19You should edit the submission description to make https://www.pullrequest.com/ a clickable link. I've seen that done for other Launch HN submissions.