Hacker News new | past | comments | ask | show | jobs | submit login

I wouldn’t really say it’s a big implementation. I just use a piece of paper and denote a line to each 30 mins of the work day.

So it might look like:

10: meeting

1030: bug fixing

11: bug fixing

1130: bug fixing

12: run

1230: run

1: lunch

130: feature work

2: feature work

230: meeting

3: feature work

330: feature work

4: plan next week

The above was my entry from last Friday, where I had a late start to the day.

At the start of my day I had kept the 12-2:30 block fairly empty (I knew some form of working out + lunch would show up, and I had wanted to do some feature work that day, but I didn’t know if any other meetings would pop up. They didn’t, so it worked great!)

I basically fill in meetings first, then work around them to put in the work I want to focus on for the day. The main caveat is I don’t focus on anything else for this blocks, and unless I’m in incredible flow and the task is definitely important, I always make sure I stop at the end of the block time (the whole “we will fill up whatever time we allot ourselves” theory).




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: