Fragmented thinking is a bigger threat to flow state than interruptions

Original Article ↗ Hacker News Discussion ↗

Commit messages, documentation, and flow

  • Example of “boring tasks breaking flow” (commit messages) is heavily debated.
  • Some say commit messages are natural punctuation between “units of work” and can even support flow by clarifying intent, enabling future understanding, and helping with rollback.
  • Others see rich commit messages as busywork, redundant with PRs, tickets, and chat; they argue demanding them can be selfish optimization of one person’s workflow.
  • Counterargument: external systems (Jira, Slack) are fragile or ephemeral; commit messages and checked‑in docs are the only durable, code-local record of why a change happened.
  • Several describe “literate” commit histories as a powerful tool for working with legacy code and as a way to re‑shape messy exploratory work into a clean narrative.

Internal vs external interruptions

  • Many agree the interesting idea is that interruptions are often internal (mind wandering, premature refactoring, boredom, waiting for builds/tests) rather than just notifications and coworkers.
  • There is sharp disagreement on which is easier to control:
    • One side: external distractions are easier (headphones, negotiation, job changes); internal ADHD/anxiety/“monkey mind” are hard, lifelong struggles.
    • Other side: not having to fight external interruptions at least removes one whole class of problems; you always have to deal with internal issues anyway.
  • Long subthread debates whether one can train focus (via meditation, habits, drugs) versus the mind being fundamentally unruly.

Reception of the article

  • Positive readers say it captures their lived experience of “fragmented thinking” and helps them notice internal process-level interruptions.
  • Critics find “fragmented thinking” poorly defined, the piece repetitive and padded, with a style reminiscent of AI-generated text.
  • Some question the strength of the cited research (mostly self-report surveys) and view the causal claims about flow as overreaching or “hogwash.”

Managing focus: tools, habits, environments

  • Suggested tactics:
    • Block distracting sites (Cold Turkey, /etc/hosts, uBlock), use RSS to slow consumption.
    • Classic Pomodoro with a written log of internal interruptions.
    • Notes, milestones, and end-of-day reflections to rebuild context after inevitable interruptions.
    • Good documentation (often written first) so work can resume or be handed off smoothly.
    • Whiteboard/pen-and-paper design to reduce cognitive load and keep state out of working memory.
    • Structured habits and “muscle memory” for routine tasks.
    • Pink/brown noise with ANC, offices with doors, or WFH to reduce ambient disruption.

Nature and value of flow

  • Some report “best days” as 5–10 hours of uninterrupted flow and deliberately engineer months of minimal contact to achieve that.
  • Others find flow overhyped: mental fatigue and internal distraction may just mean it’s time for a break; productivity also comes from walks, showers, and background processing.
  • Several note that work must be at the right challenge level; too vague or too hard encourages internal distraction, while extreme challenge simply exhausts you and rightly ends flow.
  • A few admit they’ve never felt any special “flow feeling” and just rely on “micro‑progress” (always taking the smallest next step). Replies suggest that’s likely already a form of flow, just without mystique.