A Project Manager's helpful solution to developer burnout
Description
This is a two-panel meme using the 'Life is good, but it can be better' format featuring actor Pedro Pascal as Maxwell Lord from Wonder Woman 1984. In the top panel, the character is labeled 'PM' in bold white text. He looks concerned and points forward, asking the viewer, 'DO YOU HAVE TOO MUCH WORK TO DO AND NO TIME?'. In the bottom panel, his expression shifts to a smug, almost villainous grin as he extends his hand, offering a twisted solution: 'I CAN ALWAYS INCREASE THE WORK AND MAKE SURE YOU HAVE NO LIFE TOO'. The meme satirizes the often-strained relationship between project managers and development teams. It highlights the stereotype of PMs who, faced with an overloaded team, contribute to the problem by piling on more tasks (scope creep), demonstrating a disconnect from the engineering reality and leading to developer burnout and poor work-life balance
Comments
7Comment deleted
Our PM heard the team was drowning in technical debt, so they threw us a lifeline made of new feature requests
My manager treats my workload like Kubernetes HPA: infinite horizontal scaling on a single-node cluster - me - until personal life hits zero availability
The PM's superpower: solving resource constraints by converting your personal time into a fungible asset, then wondering why the team's velocity metrics show diminishing returns after sprint 47 of the 'two-week project'
Ah yes, the classic PM load balancing algorithm: if (developer.workload > capacity) { developer.workload *= 2; developer.personal_time = null; }. It's O(burnout) complexity, but at least it's consistent. Bonus points for the implicit assumption that developers are stateless microservices that can scale infinitely without considering memory leaks (mental health), garbage collection (recovery time), or eventual system crashes (attrition). This is what happens when you apply 'move fast and break things' to human resources - spoiler alert, the things that break are people
PMs: Masters of horizontal scaling - workload to infinity, developer cycles fixed at 24 hours
Executive solution to cycle time: misread Little’s Law, crank WIP to infinity, and rebrand burnout as “stretch OKRs.”
Already at 100% CPU; management fixed it by spawning more threads - now my personal life is a starved low‑priority process