Nos comentários a este post da reason sobre o livro de Graeber, talvez a melhor explicação para a existencia de empregos que há primeira vista parecem não ter grande utilidade:
«Most days I end up with 2-3 hours of work to be done over an 8 hour period. The rest of the 8 hours is spent being readily available in case something comes up.»
e
«Exactly. We are in a development lull at work right now. Some weeks I am purely, "in case shit happens". I can fix it quickly. I know the processes, the flows, the fixes. Bringing someone in to replace me at a much lower cost, can become a problem "when shit happens". How do you even train someone on things that weren't expected? And if there is new development in a year, I require no training to start working on it. So while some would say that writing this, while being paid, is an inefficiency, it's not. You can't discount people who are trained for bad things that may never happen. And with automation, that is going to be an increasingly common job. I make up work for myself sometimes. Converting code to a different language for no reason other than it forces me to review old code.»
Tuesday, January 29, 2019
Sobre os "bullshit jobs"
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment