Re:Effective Practices for Working with a Code Reviewer
by mr_puzzled on Wednesday December 02, 2020 @09:37PM
(#25284609)
Don't live tweet your HN submission, it's a shitty way to get followers to upvote the submission even if you didn't mean to do that. Next time, save your tweets for 12+ hours after submission and post it on twitter.
[ Parent
| on HN ]
Re:Effective Practices for Working with a Code Reviewer
by mtlynch on Thursday December 03, 2020 @10:43AM
(#25289918)
I tweeted my entire publish-day process,[0] which included re-reading my post, sending an email to my newsletter subscribers, and posting to social media, including HN. I never linked to HN or even suggested that anyone find my post here.
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 [email protected] and we'll look at the data.
[0] https://twitter.com/deliberatecoder/status/13341560121321185...