Comment by jraph
1 day ago
Yep.
When there are no clear tasks, I sometime leave a syntax error at the place work should continue tomorrow. This is quite effective. It can make the answer to the "Where was I?" question immediate instead of taking a few seconds and this is one fewer barrier.
Yes. It's funny how this kind of trick can instantly snap the entire working context back into your mind. Essentially leaving you free to forget about the context during your free time and overnight. Truly a useful "hack".
It's also useful to jot down a quick list of (say) three items that are at the top of your mind when you leave work for the day, and they too will help with a context restore.
Also just chuck Todo comments in the code
The magic of Git means you can immediately find them in the working index and get back on to it. Just remember to remove them before the commit.
> The magic of Git means you can immediately find them in the working index
How does git help you find certain texts in files? `grep` should do the trick just fine, unless I misunderstand what "chuck Todo comments in the code" mean, the code lives on your disk no?
6 replies →
If you do this often enough you can create a simple commit hook that searches for these markers and will fail to commit if it finds them.
"focus division multiplexing"
I've done that too. Especially if I have to stop working, but I'm in the middle of something. There are no compilation errors or tests failing but the feature isn't completed.
Introducing a syntax error is like a saved game, portal back in time. I'll come back to it tomorrow and it'll take me max one minute to reload the context into my brain.
Another similar thing is to leave an easy sentence half-finished so when you come back to it, there's an obvious first thing to do and hop back in.
I've always used "$$". It's probably a subliminal thing.
I like this. Good trick.
#pragma warning
I always leave work( for lunch, for home) at failing test . Try to anyways.