<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Context Switching on Daniel Eisenhardt</title><link>https://danieleisenhardt.nl/tags/context-switching/</link><description>Recent content in Context Switching on Daniel Eisenhardt</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 22 Mar 2026 11:30:00 +0200</lastBuildDate><atom:link href="https://danieleisenhardt.nl/tags/context-switching/index.xml" rel="self" type="application/rss+xml"/><item><title>The Hidden Cost of Slow Feedback</title><link>https://danieleisenhardt.nl/posts/the-hidden-cost-of-slow-feedback/</link><pubDate>Sun, 22 Mar 2026 11:30:00 +0200</pubDate><guid>https://danieleisenhardt.nl/posts/the-hidden-cost-of-slow-feedback/</guid><description>Software developers hold a lot of information in their head while working. Any serious interruption means they lose their train of thought and have to start over. This was already explained in The Mythical Man-Month, which came out in 1975 (over fifty years ago by now!). The same concept is expressed regularly in articles such as Maker&amp;rsquo;s Schedule, Manager&amp;rsquo;s Schedule by Paul Graham in 2009.
By now software professionals know not to interrupt their colleague without good reason, but what about the interruptions we inflict on ourselves?</description></item></channel></rss>