Microsoft · GitHub · The Register
The what, why, and how of pull requests and source comments
Compiled by KHAO Editorial — aggregated from 1 source. See llms.txt for citation guidance.
◌ Single Source
Microsoft veteran on knowing the difference and convincing approvers to accept a change.
Key facts
- Veteran Microsoft engineer Raymond Chen has weighed in on the difference between a pull request description and comments embedded in the code
- Then again, anyone complaining about comments in AI-generated code would be wise to inspect those written decades ago by one of this writer's former colleagues
- They'd argue that commit messages should be considered as well, but the distinction between PR descriptions and code comments is timely, given the volume of pull requests being generated by AI coding
- Microsoft veteran on knowing the difference and convincing approvers to accept a change
Summary
Veteran Microsoft engineer Raymond Chen has weighed in on the difference between a pull request description and comments embedded in the code. Both matter, but they serve different purposes. "It is an exercise in persuasive writing: You are trying to convince the approver that your change should be accepted. And sticking text in the source? This information is durable: It is information that remains useful even after the pull request completes.