Hacker News new | ask | show | jobs
by kfrzcode 3294 days ago
I'm a freelancer, and I set my own schedule.

I've logged virtually everything I've done in the past three years into Google Calendar. This is a way to get feedback on my actions, rather than listing my intentions.

If it's a task I need to do daily, I build it into my morning or nightly routine. For example, my "sit down at desk" routine is to review and block out my time for the day in gcal. If it's not important enough that I don't remember it, don't have an automatic email reminder or it's not already on my calendar, than it's not important enough for me to think about.

I also have built a habit of "frontloading" work, and doing necessary but distracting (domestic) things as soon as possible so they are off of my plate.

Giving full concentration to tasks in my brain requires multi day thinking, so I have to sort of 'soak' in the project context. For concrete deliverable based tasks in development I'll use whichever PMS is appropriate and block/log my time appropriately.

I have a dev-journal.org for things I want to remember or side project tangents I'll want to go down later, as well as tracking arcane bash commands I rarely use etc.

I used to use iCal (I find it superior to gcal for many reasons) until I moved to using Debian full time.

1 comments

So do you put current or future tasks on your Google Calendar, with expected start and end times, at the level of feature to be implemented, say (assuming you mostly a coder)?