News for hackers. Stuff that matters.
Re:Tell HN: My best productivity hack by makmanalp on Monday April 16, 2018 @08:19PM (#16854273)
This, and also marking which one is the worst one, so I do that one first without slacking off and then the rest is easy.

The other thing is that I usually leave a context file (which says "you were adding X to function Y and then debugging Z") in whatever directory I'm working in so that I remember what I was doing if I was in the middle of something.

Re:Tell HN: My best productivity hack by majewsky on Tuesday April 17, 2018 @05:33AM (#16856775)
I usually just write "TODO have not done X and Y yet" into the source file that where I was last working. It's deliberately not a comment, so that I can find it by running `make` and looking for the syntax error.
Re:Tell HN: My best productivity hack by pvinis on Tuesday April 17, 2018 @08:49AM (#16857767)
haha I do that too. If I need to leave something as it is but I need to fix it, I just write what I should do but without a "//" so it doesn't compile next day when I press build without thinking.