<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Productivity on Kliku Kliku</title><link>https://klikukliku.dev/tags/productivity/</link><description>Recent content in Productivity on Kliku Kliku</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 24 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://klikukliku.dev/tags/productivity/index.xml" rel="self" type="application/rss+xml"/><item><title>A focus framework: The Pomodoro technique</title><link>https://klikukliku.dev/posts/pomodoro-technique/</link><pubDate>Tue, 24 Mar 2026 00:00:00 +0000</pubDate><guid>https://klikukliku.dev/posts/pomodoro-technique/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Have you ever wondered why your productivity drops so much after just a few hours of coding? I noticed something in my own workflow: the biggest enemy of focus isn&amp;rsquo;t a lack of knowledge. It is constant context switching.&lt;/p&gt;
&lt;p&gt;Chat messages, emails, and &amp;ldquo;quick questions&amp;rdquo; from teammates constantly break our rhythm. I decided to look for a solution, and for the past few weeks, I have been testing the Pomodoro technique. Today, I want to share my findings with you.&lt;/p&gt;</description></item></channel></rss>