- How do you measure that by reading the code before comitting you are actually improving it? If people would ask for a review (which seems natural for me)
- First time opening a pull request, then a comment would be made so he knows what to do. If you haven't asked for a review yet, that message would be given to you for so long, before you learn to ask.
- Hey, have you read our contributing guide? It contains the basic to get you started before asking for a review. It's ok to go through it and ask for a review later on.
- If you didn't ask for a review and some other person has started reviewing, will ask you why?
- Figuring out that you haven't read your code before asking for a review, it's rather simple because we can look at pull requests and see what's the medium time of asking for a review.
- If you connect with hipchat it might make a fully integrated solution by reading logs and seeing you are asking for a review.
- Figure out people who don't have a code review for their branches.
- Adding categories to code review comments in order to make those actionable. The purpose of code review is to help us learn, how are we measuring if this process is effective?
- An early warning system by doing coverage over the particular area of code you are commiting to. Trying to let you know you should start doing TDD if it's a new file. Then measuring the efectiveness of the message to see if the person has actually read it.
- Measuring how well we practice TDD. We write the tests first and commit failing tests. Commit atomicity.
- Use plain english, run language detection
- It should contain at least one verb in the present tense
- Compute commit atomicity by the number of changes
- Don't commit broken code by running what he has commited
- Figure out who's not practicing TDD at all and help them improve. It's actionable because it helps developers improve with a small dose of TDD every day. A learning platform for developers. You learn by doing.
- A gentle nudge to improve us as a team. When you are commenting on a line of code, you could hash tag it with something. During his reviews, we will notice stuff about ourselves and see if we can improve
http://www.stellman-greene.com/aspm/content/view/33/40/
http://meta.codereview.stackexchange.com/questions/755/someones-code-too-bad-to-review?atw=1
http://meta.codereview.stackexchange.com/questions/1320/best-of-code-review-2013
http://blog.smartbear.com/code-review/having-some-fun-with-code-review/
- First time opening a pull request, then a comment would be made so he knows what to do. If you haven't asked for a review yet, that message would be given to you for so long, before you learn to ask.
- Hey, have you read our contributing guide? It contains the basic to get you started before asking for a review. It's ok to go through it and ask for a review later on.
- If you didn't ask for a review and some other person has started reviewing, will ask you why?
- Figuring out that you haven't read your code before asking for a review, it's rather simple because we can look at pull requests and see what's the medium time of asking for a review.
- If you connect with hipchat it might make a fully integrated solution by reading logs and seeing you are asking for a review.
- Figure out people who don't have a code review for their branches.
- Adding categories to code review comments in order to make those actionable. The purpose of code review is to help us learn, how are we measuring if this process is effective?
- An early warning system by doing coverage over the particular area of code you are commiting to. Trying to let you know you should start doing TDD if it's a new file. Then measuring the efectiveness of the message to see if the person has actually read it.
- Measuring how well we practice TDD. We write the tests first and commit failing tests. Commit atomicity.
- Use plain english, run language detection
- It should contain at least one verb in the present tense
- Compute commit atomicity by the number of changes
- Don't commit broken code by running what he has commited
- Figure out who's not practicing TDD at all and help them improve. It's actionable because it helps developers improve with a small dose of TDD every day. A learning platform for developers. You learn by doing.
- A gentle nudge to improve us as a team. When you are commenting on a line of code, you could hash tag it with something. During his reviews, we will notice stuff about ourselves and see if we can improve
http://www.stellman-greene.com/aspm/content/view/33/40/
http://meta.codereview.stackexchange.com/questions/755/someones-code-too-bad-to-review?atw=1
http://meta.codereview.stackexchange.com/questions/1320/best-of-code-review-2013
http://blog.smartbear.com/code-review/having-some-fun-with-code-review/