A new personal post titled “Retiring from tech to live offline” from Simon Willison sparked a familiar question: do we really need to quit the internet to feel human again? Whether you’re an indie dev or a team lead, here are practical moves to make tech sustainable—without walking away. Source: simonwillison.net.
Why this resonates now
Burnout isn’t a vibe; it’s recognized by the WHO as an occupational phenomenon tied to chronic workplace stress. See the ICD‑11 note from WHO for definition and context: WHO.
Meanwhile, knowledge workers report rising “digital debt” from nonstop pings and meetings (see Microsoft’s Work Trend Index: WorkLab). The goal isn’t escapism—it’s designing healthier defaults.
7 ways to reclaim focus without quitting tech
- Protect maker time: Block 2–3 hour focus windows daily. Stack meetings into afternoons; decline or shorten invites without clear agendas.
- Notification zero: Turn off non-essential banners/badges. Batch-check comms (e.g., 11:30, 2:30, 4:30). Keep “VIP” exceptions for true urgency.
- Async-first defaults: Write a one‑pager instead of calling a meeting. Use threads and docs; reserve live calls for decisions or alignment.
- Weekend firewall: Use schedule-send after hours. Publish team norms for response times so “late-night typing” never implies “right-now reply.”
- Single‑task devices: Try an e‑ink reader for longform, or set “feature‑phone hours.” Put social apps behind a time-locked folder or secondary device.
- Local‑first AI: Run models on your machine for privacy and offline flow (e.g., Ollama or LM Studio) to avoid web distractions while prototyping.
- Quarterly reset: Take a 48‑hour offline mini‑retreat. Review your calendar, tools, and habits; cut what no longer serves your goals.
For team leads: paste‑ready Focus Policy
- No‑meeting mornings Tue–Thu; record looms for status, meet for blockers.
- Docs before decks: a 1‑page brief precedes any new meeting.
- Slack/Teams: default to threads; mark “FYI,” “Question,” or “Decision.”
- After hours: schedule‑send by default; 911‑level items = phone call only.
- Response SLAs: business hours 24h for async; emergencies defined in writing.
Measure what matters
- Meeting load: total hours/week; aim to reduce by 20–30% over a quarter.
- Context switches/hour: track with Screen Time or ActivityWatch.
- Notifications/day: target a 50% cut by trimming sources and batching.
- After‑hours messages sent: set a weekly cap; move to schedule‑send.
- Deep‑work blocks: 2–3 sessions of 90–120 minutes per day.
Simple tools help: OS Focus Modes, Screen Time/Digital Wellbeing, and distraction blockers. For local AI, see Ollama and LM Studio.
The takeaway
You don’t need to retire from tech to reclaim your attention. Treat focus as an ops problem: set policies, make async the default, minimize pings, and measure progress.
Get weekly, no‑fluff playbooks like this—subscribe to The AI Nuggets newsletter: theainuggets.com/newsletter.
