The outline structure makes this easy to skim. Thank you!
I like this. The actionable points are a bit buried in the prose, but you describe two ways of going astray that I hadn't thought about. Thank you!
One thing I would always mention is that false negatives are less costly in hiring than false positives. But I guess the article is written for an intermediate level of hiring skill, so that point is taken for granted.
It's long, but it looks like Rethink Priorities have put a lot of thought into this job posting: https://careers.rethinkpriorities.org/en/postings/8588ecc5-3e26-4086-bdb2-fe9a2eb43252
By the way, another thing one might try: Adding salt during the soaking and again during the cooking. Perhaps one teaspoon per kg of beans. In my experience, it also reduces cooking times. I haven't evaluated it rigorously, though.
Perhaps it's because of farts? I hope I don't get downvoted for bringing this up
– it's serious and, I suspect, a major inconvenience for people who cook beans
It could be that cooking beans for a long time (maybe combined with regular
skimming or whatever other techniques we don't know about) makes them cause way
less flatulence than soaking them in little water and cooking for a short time.
People recommend soaking for reducing beans' gas-generation potential, but in my
experience (yes, I've used a tally counter to count my farts under different
soaking and cooking conditions and bean species, but obviously N=1) it takes a
lot of soaking water to do that. I've found 7 l for 500 g of dry beans to work
decently. After soaking I drain and then cook in a small amount of water.
And soaking with a lot of water has implications that might not work for
Speaking of dinner: If you eat three meals with beans per day, you'll have two
or three containers going for soaking. It's likely easier to have one pot over
the fire that just gets restarted soon after each meal. (Assuming that
refrigeration is hard to come by in Uganda.)
Further practical issues:
Personally, I do soak and use a pressure cooker. But perhaps that's a luxury.
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.  It can be addition to your points about how to give feedback.
Another important skill for supervising translators:
And if the translators are semi-professionals drawn from the community:
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.)