Finding more persuasive, less manipulative ways to give pull request feedback.

Thoughtbot's platform is a central hub for software developers and product designers, offering insights into product development, design thinking, and agile methodologies. Through articles, case studies, and design sprints, Thoughtbot offers insights into user research, prototyping, and usability testing. Readers can learn about lean product development, iterative design processes, and cross-functional collaboration to create user-centric digital products and services.

thoughbot

The best possible upgrade for small code style changes would be to use linting tools to define style expectations. If a new team member is missing some context on an old decision, sharing how and when these decisions were made can help. Be Friendly and Persuasive our communication style in pull request reviews matters.

Don't Review PRs Like a Space Wizard

Ugh… Where to start. Your only real argument/complaint is this so-called “Jedi Mind Trick.” And really, that’s just you not understanding what the person means. It’s not their fault, but yours, as this is a really common way to phrase things in English.
In the example, “we” is obviously meant as a reference to the company or project. So they’re merely stating that “this company/project doesn’t do it this way.” It’s not peer pressure at all, but stating convention. There is absolutely nothing wrong with informing someone of the convention.
While I think the right way would be something more like, “Per convention, don’t use default export,” I can appreciate that the PR author may already know (or should know) this fact and doesn’t need such strict wording from the PR reviewer.
Simply understanding that makes the rest of the article moot.

Very nice approach, i usually do that

I can’t help but laugh at “space wizard”