AI sabbath
Definition: proposed mandate for two days per week of deliberate non-AI coding. The mandate includes slower pace, skill honing, employee decides AI usage (including zero), and rest from AI psychosis and skill atrophy.
Origin
2026-10-04-youtube-ai-skeptic-sabbath: framed as labor protection parallel to nineteenth-century weekend movement: “In the late nineteenth century, workers in Britain and the United States fought for shorter hours and rest days. They won, and that eventually led to the innovation of the two-day weekend.”
Structure
- Two days/week: employee controls pace and AI usage (including none)
- Skill honing: active practice of critical thinking and coding
- Rest from AI psychosis: break from over-trust pressure
- Long-term productivity argument: if AI is only as good as engineers using it, weakening the workforce is self-defeating
Rhetorical frame
Not “resistance” but “sustainability.” The weekend wasn’t anti-work. It made work sustainable. AI Sabbath isn’t anti-AI. It makes AI use sustainable by preserving the human capability that makes AI valuable.
Current status
“Until AI Sabbath becomes law, I fear they leave us no choice. Malicious compliance coupled with secretly writing code at work while everyone waits for the grand catastrophe.”
Related
- skill-atrophy-ai: the problem it addresses
- ai-psychosis: the psychological state it interrupts
- malicious-compliance-ai: the interim individual tactic