Written with AI assistance from the source video. The video is the authority.
Log in to leave a comment
No posts yet
When you come home after work, your brain feels foggy. It's not because you lack willpower. It's because your prefrontal cortex energy is already depleted from 8 hours of architecture design and troubleshooting.
According to Sophie Leroy's research, unresolved tasks linger in the mind and keep background processes running. If you briefly check Slack or email in this state, the context-switching cost explodes. Professor Gloria Mark's research team found that it takes an average of 23 minutes and 15 minutes to return to deep work after being interrupted by digital distractions. The American Psychological Association also warns that frequent task switching can wipe out up to 40% of productive time in a day. For those of us who only have about 2 hours available a day, a few notifications simply burn away the remaining time.
Just looking at a smartphone eats away at your brain. Experiments by Adrian Ward's research team showed that even when a smartphone is powered off and turned face down on a desk, working memory capacity decreases. The moment a phone enters your field of view, your brain subconsciously expends energy suppressing the urge to look at it. Instead of trying to survive on willpower, you need to clear off your desk in the first place.
Let's block website access at the operating system level. By modifying the hosts file to map social media or news site addresses to 127.0.0.1, access is physically blocked at the system level. On a Mac, open the terminal and run a script to touch the hosts file with sudo privileges, and on Windows, finish the block using PowerShell along with the ipconfig /flushdns command. Registering this script to a single shortcut lets you create an immersive environment in just 3 seconds.
Throw your smartphone into a drawer in another room where your workspace is completely out of sight. Put an analog timer on your desk instead of your smartphone. Completely separate the profiles for your coding browser and your writing browser. Leave only a single Markdown editor open in your writing profile.
Since you don't have time, throw away complex writing techniques. Right before leaving work, leave a single-line memo in Markdown based on the technical issue you solved that day. When you come home and sit at your desk, don't touch messengers and turn on your local Markdown editor. Set a timer for 30 minutes and push out a draft in the form of a brain dump without thinking about grammar.
On Saturday morning, invest just 10 minutes to review the Git commits and pull requests accumulated over the week. Pick a useful memo from here and classify it into one of three categories: troubleshooting, architecture, or technical exploration. Don't waste time making thumbnails or fixing CSS. A single Markdown template focused purely on text is enough.
The biggest mistake developers make is spending all their time building their own blog framework or picking themes. Refining your pipeline when you haven't even accumulated 10 articles is just running away. Just use an existing platform and forbid style modifications for a while.
Abandon the idea of writing every day. You just need to stick to publishing once a week. On days when your energy is drained, like Wednesday or Thursday, skip writing altogether and consolidate and refine over the weekend. Running this system allows you to leave development records every week without relying on willpower.
