Already slipping on my weekly review process, woops. I'm going to do it though, and I'm going to keep doing it until it's a habit.
I fucked up on tracking last week. Big time. I tracked 32:45 of 168 hours, which is just under 20% of my time logged. That doesn't even include the time I'm working on this post right now, just to show how bad I'm doing with tracking right now.
Of the time tracked:
|3:12||General Organizational State||1.90|
|0:24||Habit Forming and Management||0.24|
|4:55||DnD night at work||2.93|
|10.30||All Time Tracked||Time%|
|06:39||tasks related to Datacenter Failover strategies||3.96|
|3:28||tasks related to monitor and on-call training||2.06|
|0:11||tasks related to internal Node.js packages||0.11|
|0:06||tasks related to Release Process||0.06|
|23.93||Work Time Tracked||Time%|
I didn't do too much reading last week; I have a bunch of things on my reading list that I need to chew through this week, so next week should be a fat set of materials.
Man. I really have to get better at clocking. I have Tasker logging metrics from my phone, such as when I leave work and home, GPS logs, and IP address; I'm planning to set up a system which SCPs that data to my server, which then processes them and pulls them in to an Org mode file which I can use to infer clocking. Along those lines, I'm planning to set up a Tasker scene to allow me to quickly capture, since I can't really get Mobile Org to work reliably right now.
I have a tonne of plans this week for personal development projects, and personal upkeep, I need to use this week as a perfect example of how to clock well, so that I can look ahead and feel comfortable with it.