Skip to content
 
If you can read this, either the style sheet didn't load or you have an older browser that doesn't support style sheets. Try clearing your browser cache and refreshing the page.

(AsiaOne) Hero After sharp criticism, Tencent announces the end of the 20-hour work shift. Correction: After sharp criticism, Tencent announces that celebrating a worker's 20-hour work shift will not be tolerated as much as before   (asiaone.com) divider line
    More: Hero, China, Working time, Tencent Holdings Ltd, Alibaba Group, work group chat, Fole Zhang Yifei, work-life balance, Tencent Holdings employee  
•       •       •

1232 clicks; posted to Business » on 29 Jan 2022 at 12:30 AM (16 weeks ago)   |   Favorite    |   share:  Share on Twitter share via Email Share on Facebook



20 Comments     (+0 »)
View Voting Results: Smartest and Funniest
 
2022-01-29 3:40:08 AM  
media.tenor.comView Full Size
 
2022-01-29 4:19:06 AM  
After the first 10 hour shift, they get in a machine and work the next ten hours backwards, so it all evens out.
 
2022-01-29 5:57:19 AM  
Surprised more of them are not going to the laying down movement
 
2022-01-29 6:52:52 AM  
My longest work "day" was 28 hours straight with a total of 45 hours worked over a 54 hour stretch.  This was at a nuclear power plant taking a direct hit from a hurricane so it was important work.
 
2022-01-29 8:05:39 AM  
So, CCP lover subby gives this the hero tag because.........why?
 
DVD
2022-01-29 8:39:35 AM  

lifeslammer: So, CCP lover subby gives this the hero tag because.........why?


It raises his Social Credit Score to do so?
 
2022-01-29 8:57:35 AM  
Suffice to say, Tencent's work/life policy isn't worth a dime.
 
2022-01-29 9:13:42 AM  

groppet: Surprised more of them are not going to the laying down movement


Doesn't it translate as "lying flat"?
 
2022-01-29 10:14:40 AM  
Wait until they hear about the work policies of 50 Cent
 
2022-01-29 11:35:25 AM  

lifeslammer: So, CCP lover subby gives this the hero tag because.........why?


becasue like most people that act without critical thinking, they assumed sarcasm was a thing they could do, in the open public, among total strangers that do not know them from a full on hood wearing racist klan shiatwhiff.


Sarcasm = the juxtaposition between who you really are with what you just said.

So of course when no one actually knows who you really are first, then now they know who you are from whatever it was you just said.

Think of sarcasm as an inside joke. It's a joke only for pole who already really do know who you are. So when you are among strangers, the situation does not actually allow for the use of sarcasm.
You are trying to tell an inside joke to people who are not already in on it.


You can also imagine sarcasm as a reference joke, where the needed upfront knowledge to get the referent, is who you are, what your POV/ideology actually is.
When we understand the mechanical functions of various humors, we tend to leverage them a whole lot better.And sarcasm is one very few seem to grasp well. Treating it as if it were more of a pop culture reference joke that of course the bulk of people, who don't know the speaker at all, would be in on with them somehow.
 
2022-01-29 11:51:14 AM  

bighairyguy: My longest work "day" was 28 hours straight with a total of 45 hours worked over a 54 hour stretch.  This was at a nuclear power plant taking a direct hit from a hurricane so it was important work.


Why would you build a nuclear power plant where it could be hit by a hurricane?
 
2022-01-29 11:56:33 AM  

foo monkey: After the first 10 hour shift, they get in a machine and work the next ten hours backwards, so it all evens out.


Most murcan workers are just hitting their stride after 10 hours.  Fatigue and burnout are for losers.
 
2022-01-29 11:59:09 AM  

ablank: Wait until they hear about the work policies of 50 Cent


Or the 1%.

Which is largely work free.
 
2022-01-29 11:59:33 AM  

TedCruz'sCrazyDad: bighairyguy: My longest work "day" was 28 hours straight with a total of 45 hours worked over a 54 hour stretch.  This was at a nuclear power plant taking a direct hit from a hurricane so it was important work.

Why would you build a nuclear power plant where it could be hit by a hurricane?


I didn't build it, I just worked there.

There's bunches of them.  I was at the Brunswick Plant by the NC/SC border.
Fark user imageView Full Size


Hurricane in question
 
2022-01-29 11:59:57 AM  

TedCruz'sCrazyDad: bighairyguy: My longest work "day" was 28 hours straight with a total of 45 hours worked over a 54 hour stretch.  This was at a nuclear power plant taking a direct hit from a hurricane so it was important work.

Why would you build a nuclear power plant where it could be hit by a hurricane?


Food for thought.

Good one
 
2022-01-29 12:11:32 PM  

TedCruz'sCrazyDad: bighairyguy: My longest work "day" was 28 hours straight with a total of 45 hours worked over a 54 hour stretch.  This was at a nuclear power plant taking a direct hit from a hurricane so it was important work.

Why would you build a nuclear power plant where it could be hit by a hurricane?


Same reasons you'd build it in a place that is prone to earthquakes or tornadoes. You're close to a population center than needs large amounts of electric power. Also being near the coast means you have a large body of water to act as a heat sink.
 
2022-01-29 12:21:55 PM  
The longest shift I've worked was 28 hours, solo, nonstop, without breaks. I was managing a K-Hole in PHX, the Dm insisted on approving all new hires right before leaving for a three week sabbatical. Had to fire my graveyard workers for theft, leaving me to fill the shift alone while also pulling my normal shift along with books and deposits, etc.

Four days in a row of 16 hours straight, followed by a 28 hour shift. 92 hours in five days- on salary.

I called in my resignation, left the keys on the counter of the office, and walked out.
 
2022-01-29 6:16:35 PM  

bighairyguy: TedCruz'sCrazyDad: bighairyguy: My longest work "day" was 28 hours straight with a total of 45 hours worked over a 54 hour stretch.  This was at a nuclear power plant taking a direct hit from a hurricane so it was important work.

Why would you build a nuclear power plant where it could be hit by a hurricane?

I didn't build it, I just worked there.

There's bunches of them.  I was at the Brunswick Plant by the NC/SC border.
[Fark user image image 425x251]

Hurricane in question


I was getting ready to ask when that happened, and I saw your link to Dana in '84. My folks "retired" in '00, and then traveled around the country in an RV doing nuclear plant shutdowns, and did it for 15-16 years. Dad is a civil engineer that graduated magna cum laude with a masters from UMR (back when it was still called that and ranked in the top 100) and retired after 30 years at mo-dot, so he ended up being a safety/ANSI compliance engineer for the shutdowns. Mom retired from dept of elementary and secondary education for MO, so she did payroll. They worked crazy stupid hours for their age, but would hang around whatever location they were at for a month before and or after and travel. But yeah, lots of 12-15+/hr shifts for sure
 
2022-01-30 11:10:33 AM  

bighairyguy: My longest work "day" was 28 hours straight with a total of 45 hours worked over a 54 hour stretch.  This was at a nuclear power plant taking a direct hit from a hurricane so it was important work.


43 hours straight was my record.

Botched data migration.  Knew 2 hours into the migration attempt (hour 10 of that stretch, so we're talking about 10pm Friday night) that given the brain dead migration process a colleague (I'd already expressed concerns earlier, that week, the week before, the month before) had come up with, we'd be some days slow in doing the migration.  I had proposed an alternative migration process, which was shiatcanned.

Well I got the green light at 10pm, when I said that we're not going to finish by the close of the announced maintenance window at the update rate this crap migration tool was running.  As in it would complete around Wednesday evening or early Thursday morning.  I said there was a way we could get it done, but it might run just past the Sunday window.  But it would be finished long before Monday morning.

My department head (who really didn't like the guy who had built the stupid tool)  said do it.  Pretty gutsy call on his part - the cautious play would have been scrub, reschedule.  But he was ex-AF, and apparently one of the LeMay types - press home the attack.  Pulled the plug on the old migration tool - if I couldn't work a miracle we'd scrubbed the attempt at a point where no problems would exist.  I put out a list of milestones and target timeframes, with projected end time at 2pm Sunday afternoon.  Code complete around 4am Saturday morning, performance testing completed at 10am.  Updated end timeline to 10am Sunday morning.  Go-no go decision at 11am, new migration to start at noon.

Since I only had the lab numbers to go on, even that 10am timeframe was conservative, and the higher performance production environment didn't let me down.  Final object update took place Sunday morning just before 7am.  At the 8am checkpoint the team that had been put on hold Friday night was told "go" on their part of the upgrade, and 40 minutes later they confirmed their part of the upgrade worked, and the migrated data was good.  Got a 20k raise, and 3 years later the idiot who insisted on the crippled tool was fired for general incompetence.  Took 3 years of shiat reviews to get to that point, but they did get rid of him (he never triggered one of the insta-fire conditions, so it took a while).

Never again.  I think I was hallucinating on the way home.  Cows don't float in the air at 60mph usually.  Sleep deprivation is a strange thing.
 
2022-01-30 1:47:48 PM  

MadHatter500: bighairyguy: My longest work "day" was 28 hours straight with a total of 45 hours worked over a 54 hour stretch.  This was at a nuclear power plant taking a direct hit from a hurricane so it was important work.

43 hours straight was my record.

Botched data migration.  Knew 2 hours into the migration attempt (hour 10 of that stretch, so we're talking about 10pm Friday night) that given the brain dead migration process a colleague (I'd already expressed concerns earlier, that week, the week before, the month before) had come up with, we'd be some days slow in doing the migration.  I had proposed an alternative migration process, which was shiatcanned.

Well I got the green light at 10pm, when I said that we're not going to finish by the close of the announced maintenance window at the update rate this crap migration tool was running.  As in it would complete around Wednesday evening or early Thursday morning.  I said there was a way we could get it done, but it might run just past the Sunday window.  But it would be finished long before Monday morning.

My department head (who really didn't like the guy who had built the stupid tool)  said do it.  Pretty gutsy call on his part - the cautious play would have been scrub, reschedule.  But he was ex-AF, and apparently one of the LeMay types - press home the attack.  Pulled the plug on the old migration tool - if I couldn't work a miracle we'd scrubbed the attempt at a point where no problems would exist.  I put out a list of milestones and target timeframes, with projected end time at 2pm Sunday afternoon.  Code complete around 4am Saturday morning, performance testing completed at 10am.  Updated end timeline to 10am Sunday morning.  Go-no go decision at 11am, new migration to start at noon.

Since I only had the lab numbers to go on, even that 10am timeframe was conservative, and the higher performance production environment didn't let me down.  Final object update took place Sunday morning just before 7am.  At the 8am checkpoint the team that had been put on hold Friday night was told "go" on their part of the upgrade, and 40 minutes later they confirmed their part of the upgrade worked, and the migrated data was good.  Got a 20k raise, and 3 years later the idiot who insisted on the crippled tool was fired for general incompetence.  Took 3 years of shiat reviews to get to that point, but they did get rid of him (he never triggered one of the insta-fire conditions, so it took a while).

Never again.  I think I was hallucinating on the way home.  Cows don't float in the air at 60mph usually.  Sleep deprivation is a strange thing.


My longest day, perception-wise, almost 24.  Overnight server move, 12 hours+ scheduled, about 6pm-6am, not that big of a deal.  It does become a bigger deal if you go in for a root canal at 8am and there are complications.  Long story short, dentist 1 couldn't take care of the issues, referred me to dentist 2 as abscess was growing.  Tons of pain but dentist 2 did the root canal and got the abscess under control by 2pm.  I went home to try and salvage some rest / sleep before the overnight shift.  Moderate success.  I walk into work looking like I have a tennis ball stuffed in my cheek.  Recounted my day to much sympathy, along with a pool on how long I was going to last before going home.  I finished the shift, leaving at 7:30 am.  Oh, they would bring nice food for us on move nights.  So as they are bringing it in, mumbling to myself, "please be soft ... please be soft ...". It was meatloaf and mashed potatoes.  Thank you God! Afterwards, my boss said no one would ever question my work ethic after that night.
 
Displayed 20 of 20 comments

View Voting Results: Smartest and Funniest

This thread is closed to new comments.

Continue Farking




On Twitter


  1. Links are submitted by members of the Fark community.

  2. When community members submit a link, they also write a custom headline for the story.

  3. Other Farkers comment on the links. This is the number of comments. Click here to read them.

  4. Click here to submit a link.