Hacker News new | ask | show | jobs
by egypturnash 1616 days ago
I've been timeblocking on paper for years with the Pomodoro method. One crucial part of that method that's easy to overlook is the part where you look back at your records when you finish a thing and see how long it took to actually make it, versus your initial estimates; doing this helps you develop a sense of how long this kind of task will actually take!

One major leap in this for me has been developing a habit of also tracking time spent on a project somewhere in the project itself; I'm an artist, and every piece I work on now has a layer called "tracking" with a bunch of little hash-marks representing a half-hour of work, with other annotations like the date and maybe what part of complex pieces I was working on. It's now really easy to look back and say "this drawing with a complicated library background took 7h".

1 comments

Yeah - I find this super important too. I readjust my calendar entries based on actual time I spent on something so I can reflect on it later in the day.

As mentioned, we are going to add in insights/analytics for this reason