- Use the 15 minute rule to get started, only agree to do 15-20 minutes of work to see if you are flowing in that project, most of the time once you get started and loaded up the project in your mental space you can easily flow on it. Pomodoro is nice as well, but the 15 minute get started rule has less commitment needed and usually works, or just plan to do at least one tomato and you end up doing many.
- Leave a currently solved code part partially done or leave a compile issue on the area you were working on, then wake up the next day, finish that part and you can flow right into other work because the domain is in your mind.
- Multiple projects and work on another project during procrastination or a thinking spot of the current project. Have main work projects, side projects, fun projects, some are more fun, more work or just tedious/rote that you can use depending on your productivity or work style of the day.
- Motivators and triggers: music (usually a playlist that is used during work to make it more regular), coffee/gum/work food, focus by turning off distractions except for breaks, stand up regularly and walk around when stuck on any issues that need to be done, and visualize shipping.
- Creative Open/Focused Closed state: do creative work in the open state, block out time and explore, do must be done work in the closed state, minimize distractions and exploration [1].
- Start the day right, work on something simple or one check in for instance before reddit/HN/news or distractions, sometimes the first thing you do in the morning can influence your whole day, reward yourself with distractions but base yourself in production at least 2 to 1 productivity to fun/distraction.
Ultimately be a pro, a pro can start working to a high level even when they don't want to, sometimes you need to jump start or get a rolling start but you can develop a habit to get moving and ship.
[1] https://genius.com/John-cleese-lecture-on-creativity-annotat...