Richard Möhn

software developer @ Spark Wave
235 karmaJoined Mar 2019Working (6-15 years)Kagoshima, Japan


Sorted by New


Thanks for writing this analysis! I agree with a most of it. One other argument I've heard for not providing feedback after job applications is that it carries legal risk. What the risk is specifically, I don't know – perhaps a candidate could sue you for discrimination if you inadvertently choose the wrong words? A way to mitigate this risk is the phrase ‘You didn't demonstrate… [mastery of Python, facility in calming down angry customers, whatever]’. It avoids making statements about the candidate in general and instead focuses on their behaviour during the application process, which you've observed. [1] It can be addition to your points about how to give feedback.


Another important skill for supervising translators:

  • Management of production processes. (In contrast to classic project management.)

And if the translators are semi-professionals drawn from the community:

  • Leadership/management

I've seen problems from a lack of these in one translation project.

Thanks! I appreciate your comment. (Not so sure about the magnanimity. I spent a lot of time thinking about how to get my revenge.) But Harold Godsoe gave me some good advice.)

It happens often on this forum. 🤷‍♂️ (This is meant seriously, not as a reference to the mass-downvoting my article experienced.)

This whole affair has cost me way more time than anyone else, I suspect. I just wanted to have some closure. And it's not like I ‘pressured’ someone to engage on the front page. (Although for some reason, more people appear to be looking at this than I expected.)

Thanks for not deleting my comment outright, though.

Load more