Programming is a type work that invites distraction. A lot of Googling, so much advice exist on Reddit/HN which are filled with distractions, countless rabbit h

Programming is a type work that invites distraction. A lot of Googling, so much advice exist on Reddit/HN which are filled with distractions, countless rabbit holes in every language and libraries, fractions of free time during compilation, etc. I can easily read, play sports, or practice instrument for a full hours without a single moment of interruption, but it's much more difficult for programming. To mitigate that, I've employed the following tactics: 1. A browser plugin called Intention, which gently reminds me when I visit one of the sites. I love that it is a gentle reminder, because sometimes the answer I seek is on HN/Reddit. It just makes sure that I'm browsing with deliberation. 2. I have a list of stuff (relevant to the current project) to do always ready by my side. When compilation takes place, rather than context-switching to an entirely different activity, I deal with those small tasks that are still in the same project. If there's nothing else to do, I start writing notes about my current work. I find that keeping such a logbook very helpful, both in maintaining concentration, and in organizing my thoughts. Regardless of what project I'm working on, there's almost always something to work on or think about, anyway. 3. I have dedicated news-reading time where I browse my RSS feeds and HN, and stuff. It reassures my lizard brain that I'm not "missing anything". (And I'm genuinely interested in reading news, and HN). Avoid drama. 4. Physical exercise intermittently. I do a five-minute HIIT every half an hour or so. The adrenaline keeps me mentally refreshed. 5. Ultimately, it's better if you are into the thing you are working on. If you are just not interested at all, it's very difficult to force yourself to concentrate.