Then we would see how sympathetic they would be to the plight of these workers and how quickly the problem would be solved.
Then we would see how sympathetic they would be to the plight of these workers and how quickly the problem would be solved.
He rode one, from end-to-end on the line, during the heatwave, in rush hour. He came out the other end drenched in sweat, jacket hanging in his hands, looking exhausted and quickly set about resolving that problem. (Nuanced details left aside, so don't hang me fellow Torontonians)
https://www.thestar.com/news/gta/transportation/2016/09/07/j...
Doing something for a very limited amount of time, that you know has no bearing on your job performance evaluation, is extremely different from doing that thing full-time.
In some ways I think it reduced empathy in some people, because it causes some to come away with a very warped view of that job and think "Hey I did this for a week and it was fine, what're they complaining about?"
But yeah. That would be good.
I don't think the OP's suggestion does anything close to reinventing the concept of a worker cooperative.
I found Amazon's hiring practices and employee management to be very effective compared to other places I've worked. In general, I found their whole dogma really worked in practice, which surprised me at first.
Conway’s Law[1] applies. In terms of product priorities, the design needs of “contracted moderators” are somewhere below IPv6 support in the product roadmap.
What about other things like cleaning, plumbery etc. There are other terrible jobs besides moderation. Should we rotate on these also?