Here are my tricks to keep context between interruptions: 1. Navigation among uncommitted changes in git. That means - one commit per day. Right after the commit to spend ~20 minutes working on a new task. Next day, all uncommitted changes will be a good reminder. 2. My phone is always off. It lives in the kitchen. My friends know that I'm not available 24/7, but before I go to sleep I check text messages. 3. I use Chat GPT to talk. Not for coding, just for planning. Any additional thoughts and progress upon the task I'm posting there. That creates a chain of contexts (15-50 messages). 4. At the beginning of the coding session, I'm providing for Gpt a detailed list of what I'm working on, the state of progress, where are the concerns. It's a start topic. This helps me achieve a stream state immediately after I realize what is the next step is required to continue working. 5. Commit messages - it includes what is required to do next. That gives the whole tree of interrupted tasks and requirements. 6. 2 coding sessions per day by ~4 hours, sleep in between. 7. Nicotine gum 8. Listening to some podcasts during coding sessions. It works 50% of the time, esp when the problem seems "unsolvable." Looking through the logs and code until an idea appears. What is damaging: 1. Shopping spoils the whole day, so do it once per 2-3 weeks. 2. Talks with recruiters (that's my phone is off) 3. Corporate environment. 4. unplanned events. Any unplanned activity spoils at least one day when you become aware of it, one day before the event, the day of the event, and the next couple of days, when you realize that a context is lost.
yes, it's suspicious. I wouldn't be surprised if it's more market-related games.
Here are my tricks to keep context between interruptions:
1. Navigation among uncommitted changes in git. That means - one commit per day. Right after the commit to spend ~20 minutes working on a new task. Next day, all uncommitted changes will be a good reminder.
2. My phone is always off. It lives in the kitchen. My friends know that I'm not available 24/7, but before I go to sleep I check text messages.
3. I use Chat GPT to talk. Not for coding, just for planning. Any additional thoughts and progress upon the task I'm posting there. That creates a chain of contexts (15-50 messages).
4. At the beginning of the coding session, I'm providing for Gpt a detailed list of what I'm working on, the state of progress, where are the concerns. It's a start topic. This helps me achieve a stream state immediately after I realize what is the next step is required to continue working.
5. Commit messages - it includes what is required to do next. That gives the whole tree of interrupted tasks and requirements.
6. 2 coding sessions per day by ~4 hours, sleep in between.
7. Nicotine gum
8. Listening to some podcasts during coding sessions. It works 50% of the time, esp when the problem seems "unsolvable." Looking through the logs and code until an idea appears.
What is damaging:
1. Shopping spoils the whole day, so do it once per 2-3 weeks.
2. Talks with recruiters (that's my phone is off)
3. Corporate environment.
4. unplanned events. Any unplanned activity spoils at least one day when you become aware of it, one day before the event, the day of the event, and the next couple of days, when you realize that a context is lost.