ALT Writing good commit messages and pull request summaries. Chances are, you will work in an environment where you submit code changes as pull requests, describing changes. Describing these changes in a clear and concise way will help getting better feedback - by making it easy for the reviewer to understand the “why” and the “what” of the change. Doing this will also stop you from making unnecessary changes, or things that don’t make logical sense. A few things to help with this: Aim to have small commits where possible. Try to break your changes into smaller steps: each doing one specific thing. Summarize the “why” and the “what” in the pull request. Write no more than a few sentences on why you are making the change - what is the need? - and give a short overview of what you changed. Use images, where UIs have been changed. A picture is, indeed, worth a thousand words. Attach an image of the “before” and “after” states. Mention edge cases covered, and ones not covered.