<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>groovypuppy</author><text>This is the hack I use: once I’m ready to stop for the day, I figure out a solution (usually to a small bug) but I stop myself from coding it. The next day, the code just flows from my fingers to the keyboard the second I sit down. Works like a charm and I’m right back into it. Just delaying the gratification of seeing another bug crushed.</text><parent_chain></parent_chain></comment><story><title>How to return to the flow faster</title><url>https://codejamming.org/2019/how-to-return-to-flow</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>Jeff_Brown</author><text>In a nutshell: Know your goal, know what just happened, know what to do next. Maybe obvious, but I agree, critical, and a good thing to make explicit to oneself.&lt;p&gt;The author presents a lot of seemingly complex tools for this. Mine are, I believe, simpler -- a TODO list in .org mode (goal and next), and git log (for what just happened, always with --name-status to show what files were affected how, and maybe with -p to show the diff).&lt;p&gt;But you could use anything.</text><parent_chain></parent_chain></comment><story><title>How to return to the flow faster</title><url>https://codejamming.org/2019/how-to-return-to-flow</url></story>