The Manager Lifts the Feature, The Engineer Carries the Weight
Description
This meme uses a photo from a strongman competition to illustrate a common dynamic in software development. A large, muscular strongman, labeled 'Engineering Manager', is shown straining to lift a massive, round stone, which is labeled 'Non-trivial feature'. In the background, another large man with a beard looks on with a weary, resigned expression; he is labeled 'Sad engineer who has to support it'. The meme humorously captures the disparity in perspective between management and individual contributors. The manager's focus is on the 'heavy lift' of getting a complex feature developed and shipped, while the engineer in the background is already anticipating the long-term operational burden, maintenance, and on-call responsibilities that will inevitably follow
Comments
7Comment deleted
The engineering manager gets the bonus for shipping the 'non-trivial feature.' The sad engineer gets a PagerDuty alert named after it
Manager deadlifts the feature into prod for the all-hands glory, then hands the 24/7 pager to the name that’s still in git blame from 2014
The engineering manager lifts it once for the demo; the engineer carries it every on-call rotation for the next five years
The real weight isn't lifting the feature - it's the 3 AM pages when that 'non-trivial' boulder inevitably rolls back downhill in production. Management gets the photo op, engineering gets the pager duty and the privilege of explaining why a feature spec written on a napkin somehow requires distributed transactions, eventual consistency handling, and a complete rewrite of the authentication layer
Manager's git commit: world-record stone lift. Engineer's fork: eternal farmer's walk of prod support
Roadmap physics: the EM deadlifts a “non-trivial feature” into Q3; conservation of burden guarantees the on-call rotation carries its mass for the next four quarters
Management can deadlift it into prod; the PR description forgot runbooks, SLOs, and who holds the pager