Fictional problem card
Another year, same stack
You're maintaining a jQuery app. In 2026.
The scenario
You are tasked with maintaining a legacy jQuery application deep into 2026. This personal problem card injects 7 burnout points into your sprint as you struggle with aging technology. The situation highlights the absurdity of clinging to outdated stacks in modern development cycles.
How it plays
This problem card increases your burnout meter by 7 points. You must counter it using cards from the health or personal categories to mitigate the damage.
Why it feels familiar
It parodies the reality of working on legacy codebases long after the rest of the industry has moved on from the technology.
This problem card adds 7 burnout. It belongs to personal and can be countered by health, personal coping.