<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>deep-work on Curiosettee</title>
    <link>/tags/deep-work/</link>
    <description>Recent content in deep-work on Curiosettee</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 24 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/deep-work/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Developer&#39;s Guide to Deep Work</title>
      <link>/blog/the-developers-guide-to-deep-work/</link>
      <pubDate>Fri, 24 Jul 2026 00:00:00 +0000</pubDate>
      <guid>/blog/the-developers-guide-to-deep-work/</guid>
      <description>Every developer I&amp;rsquo;ve spoken with identifies the same problem: the actual work — the hard thinking, the architecture decisions, the creative problem-solving — keeps getting squeezed out by the constant noise of meetings, messages, and notifications.
Deep work is the skill of focusing on cognitively demanding tasks without interruption. It&amp;rsquo;s become increasingly rare and increasingly valuable. Here&amp;rsquo;s how to get better at it.
Why Developers Are Particularly Vulnerable The modern software development environment is designed to fragment attention:</description>
    </item>
  </channel>
</rss>
