3 ms·
Removing all barriers to entry is definitely key. This includes spin up / spin down time to even get into the groove. To whit I usually: 1. Keep a dedicated
by cik 6y ago
Removing all barriers to entry is definitely key. This includes spin up / spin down time to even get into the groove. To whit I usually:
1. Keep a dedicated desktop set (I'm running Linux) plugged into my side project.
2. In my editor I maintain a "where am I" document, and update accordingly.
3. I leave things (from a code perspective) committed and pushed.
4. I leave a specific note to myself on what I think I need to do next, based on my thinking at the time.
5. I book a meeting in my own calendar with the note from #4 so that it's forced to be in front of my face, and my desktop
There are other things, but this gets the ball rolling.
- ar_lan 6y agoI do a similar process, but yours sounds better. I literally just Slack myself a list of TODOs at the end of the day, but I sort of want to try your process. Especially with being WFH, it's easier to keep my place in specific apps. Are there any other things you do to get yourself started in flow?
- cik 6y agoNot really. Having a documented series of next steps, combined with current thoughts is as good as I can get. The only other key difference is that I treat sides much like work. I disable all my notifs across the board and aim for dedicated time. What do you do to get started in flow?