Thread regarding Wells Fargo & Co. layoffs

Quiet Quitting playbook

The “quiet quitting” playbook is well known:

  • “in a meeting” on MS Teams
  • scheduled slack, email, code at late hours
  • private calendar with blocks
  • mouse jiggler for always online
  • “this will take 2 weeks” (1 day)
  • “oh, the spec wasn’t clear”
  • many small refactors
  • “build is having issues”
  • blocked by another team
  • will take time because like “race condition”
  • “can you create a ticket for that?”
by
| 1370 views | | 9 replies (last November 21, 2024) | Reply
Post ID: @OP+1vAIZGlN

9 replies (most recent on top)

Stop responding to the first email you get for something and only start on 2nd request. Surprising how well this works. Second request never comes.

by
| | Reply
Post ID: @1mza+1vAIZGlN

they are actively monitoring for mouse jigglers - had a coworker working on that where someone had a mouse recording a 1000 clicks per minute or something.
not worth getting fired over, imo. let them chuck you and pay you severance

by
| | Reply
Post ID: @1zjx+1vAIZGlN

Also, do the absolute bare minimum; Make it 3 days a week in the office, but only stay for a few hours each day; Do all your work in a week but tell them it took a month.

by
| | Reply
Post ID: @1qda+1vAIZGlN

I'm quite fond of the "Some network change is preventing me from accessing any network resource."

Seems to happen every couple of months. Always on a busy weekend.

by
| | Reply
Post ID: @gnp+1vAIZGlN

"My teams isn't working"

by
| | Reply
Post ID: @oyp+1vAIZGlN

My dad told me long ago before I joined the military to never volunteer for anything. I have lived by that for years!

by
| | Reply
Post ID: @hpm+1vAIZGlN

Step 1 is to simply ignore. Anything and everything ignore it.

by
| | Reply
Post ID: @gxc+1vAIZGlN

Prod issue, brb - in every single team meeting

by
| | Reply
Post ID: @shi+1vAIZGlN

Add another one: “ some other team messed things up”

by
| | Reply
Post ID: @tch+1vAIZGlN

Post a reply

: