3 ms·
> Feigning feelings at work — what psychologists call “emotional labor” — can be as mentally and physically taxing as any other type of workplace stress, but fe
by ryandrake 8y ago
> Feigning feelings at work — what psychologists call “emotional labor” — can be as mentally and physically taxing as any other type of workplace stress, but few workers or employers recognize the threat
Tell that to a bricklayer. I've worked crappy service jobs and I've nailed shingles to roofs in 100+F degree heat. I'll take the fake smile job any day of the week.
> “I would come home from a day of barista-ing and my face would hurt. I thought I was just being whiny.”
One of those times when one should stick with one's initial thought.
- nkrisc 8y agoI suppose your point is that no one can hope for better working conditions as long as bricklayers exist?
- cfadvan 8y agoOne of those times when one should stick with one's initial thought. Everyone should have to work a retail job to get a sense of what a broad selection of the public is like. Everyone (who is physically able) should have to work in manual labor to get a sense of what hard work is like. Say, 6 months of each. You’d probably get a lot less whining, and people might not be such pricks to cashiers. Ideally a third period would be spent as a nurse or EMT, but that would be prohibitive in terms of training and break too many people.
- iagovar 8y agoAdd call centers to that. I basically had jobs in every position of the customer side, and it really helps you to understand many things.
- ryandrake 8y agoAgree completely. Also, (relevant to HN) everyone who writes software or designs computer products should spend some time doing tech customer support. I'm sure we'd end up with better products.
- xapata 8y agoAnd on pager duty. Fewer bugs when they wake you at 3am.
- techsupporter 8y ago> everyone who writes software or designs computer products should spend some time doing tech customer support. As someone who's done both, oh yes please, come into "the trenches" and see how customer-facing support, even at the enterprise level, is done and what demands and limitations we face. I have a story on this. I used to work support for a large technology company in the big company software division. Our support tools were pretty limited. We could get logs, we could try to make sense of them, we could ask our peers, and, In Case Of Emergency Break Glass, we could send an inquiry to the developers. This one developer for this one component kept getting upset with us about "how hard could it be" and all that. The problem was, the logs for that component were obtuse. They'd just say "ERR852019" or something like that and we couldn't have access to the source code or symbols to go look it up ourselves and our entreaties for a list of ERR codes was met with "we'll do it when we get to it." Finally, that group hired somebody new and a manager somewhere had the bright idea to send the new guy down to us (support was in a different area, many states away, as these things usually are) to see if the new guy could "straighten us out." We unloaded on him. Poor sod. But, he went away with a vision. He realized the staggering amount of time, effort, and, yes, money being spent on us sitting around getting yelled at by the customers with no real way to help them other than poking the program with a stick and seeing what happened. He championed our cause to that development team and, later, as he moved through the company, made support a priority, if not a focus. Logs stopped just saying "[DATE] [TIME] ERR91" and included full error messages and file paths and even abbreviated stack traces. Senior people on the support teams got access to source code so we could find the error strings and figure out what the program was doing. We even got mini tools we could use to tweak the program to get better logging or maybe even fix the problem for the customer instead of making the (overloaded) development team do it. And the big payoff? We bothered the development people less with "this is making a funny noise" and brought them quality bugs with, in some cases, proposed fixes that saved them time. Oh, and people from the development team started coming down to sit with us "in the trenches" once a year or so.
- donarb 8y agoI worked for a small family run car advertising magazine. The company had two departments, the sales/photography staff who sold ads to car dealers and collected info about each car and the graphics staff who put together the advertising from the car info and photos. There was always a lot of grousing between the two camps that one side did things that the other side couldn't understand and made their jobs harder. The owner devised a plan where each of the employees had to work for a few shifts with the other group to see what their jobs entailed. It made for a better understanding between them and gave each side an idea that the other jobs weren't exactly easy. Made for a better working relationship between the two groups.
- cfadvan 8y agoThat’s truly brilliant. It reminds me of the Wright Brothers, who would swap sides in arguments to represent the formerly opposing side, as a rhetorical exercise.
- megaman22 8y agoI'd shingle roofs all day if it meant not having to deal with people. People are the worst.
- frostburg 8y agoI've actually never had a job in which clients couldn't call you at any time to explain that they previously belived that they wanted x, but now want y, with y sometimes being impossible. The worst part is that gradually you learn to anticipate when this is going to happen and preemptively design stuff so that it's easier to change on random whims. Are rude clients in service jobs a worse emotional load than people that think that specs are just vague suggestions?
- annabellish 8y agoIt is not a competition to see who can suffer worst and longest, and all those who cannot win should be happy with their lot. Generally, it's a good idea to aim for improving quality of life for everyone, overall, not reducing things such that everyone is merely slightly less miserable than the worst possible misery.
- frostburg 8y ago"Solving" rude people seems very hard; automated call centers are univerally hated, for example.
- Latteland 8y agoRoofing doesn't pay that well. Most workers doing mine seemed to be English as a second language type people.
- johnchristopher 8y agoFor the same wage and the same benefits ? Give me the nails.
- Merad 8y agoI've worked at physically demanding jobs (loading trucks at UPS) and at emotionally demanding jobs (call centers). In each case for 2-3 years, so I have a decent amount of experience with both. Neither is particularly fun, but I would take the physical work every time. For me at least physical tiredness or discomfort is much easier to adapt to than the kind of soul crushing emotional exhaustion that you get from doing doing those jobs every day.
- reitanqild 8y agoI've done - been at the help desk - waited tables - worked in concrete repair (noisy and often really cold or really hit or really wet) - worked at a go-cart center (smiling to customers) - showeled tons and tons of grass and manure in smaller farm buildings where tractors where not an option. The thing that broke me was the smiling part in the gocart center. It took 6 months or so before I cried whenever I was alone. Full disclosure: the job was stressful in other ways too.