Ninety minutes after the kids are asleep is all I get and I've stopped pretending otherwise
There are a lot of posts here from people doing three hours a day. I get about ninety minutes on a good night, sometimes zero.
For a long time that made me feel like I wasn't serious about this. Then I did the maths — ninety minutes, five nights a week, is roughly thirty hours a month. That isn't nothing. It's just slower, and slower was never the same thing as failing.
The one change that helped most: I end every session by writing the exact next step, down to the file name. Saves the ten minutes I used to burn just remembering where I'd stopped.
2 comments
- 0
AnonymousAnon Thirty consistent hours a month will beat someone doing eight hours in one heroic Saturday and then nothing for a fortnight. I've been both of those people at different points and the ninety minute version is the one that actually got me anywhere.
- 0
AnonymousAnon The next-step note is so underrated. I do the same but write it as a question, like "why does the token refresh fire twice?" Picking it up the next night feels like answering someone rather than starting from cold.