Effective Practices for Working with a Code Reviewer
mtlynch.io
mtlynch.io
Even if I was subtly vote brigading, ordering me to tweet based on your preferences is not the proper way to handle the situation:
>Please don't post insinuations about astroturfing, shilling, brigading, foreign agents and the like. It degrades discussion and is usually mistaken. If you're worried about abuse, email hn@ycombinator.com and we'll look at the data.
[0] https://twitter.com/deliberatecoder/status/13341560121321185...
I've submitted it to HN with a more to-the-point title, as I thought the community might find the original title too clickbaity.
Yeah, I still participate in code reviews now that I work for myself. I receive a lot of PRs to open source repos I maintain, and I sometimes hire developers on a contract basis to take on coding tasks that are easy for me to delegate and spec out.
With open source contributions, I try to minimize my expectations of the author valuing my time as a maintainer because they're contributing work for free and a lot of them just aren't aware of how their choices affect the reviewer. But I do plan to link to this post in PR templates so that people can better understand how to contribute more effectively.
That book is actually where I learned the expression, "Dictated but not read." I'm surprised and amused that other people have the exact same association.
For anyone who's confused, it's from How to Win Friends and Influence People by Dale Carnegie: https://imgur.com/6wzlXxJ