Computer :(


Weekly Review 2015-Mar-13

I'm going to start trying to do more of these, in the vein of Sacha Chua's. It gives me a sort of impetus to be better about tracking my time, about logging my work, and thinking and introspecting about myself and my life. My hope ismidnfulhis leads me to being more mindful about what I'm up to, as well as providing me with a good log of how my time is going. The tough part about doing these for me is going to be balancing the verbosity of introspecting my work and pushing too much information publicly. I don't work at an open source company any more where I can get away this any more. So these posts may end up in two parts, one that gets rendered to the blog, and one that just sits in my ~/org along with the rest of my life. I'm making a personal promise to myself to make a habit of writing these for the next month, once a week, and then a monthly review. If any value comes from them, I will continue them.

This was a very interesting week. Work was stressful (how do I quantify that?), personal life was up and down but there were some bright spots:

  • I took the ferry to work today, which is always a bright spot in my week
  • I got a promotion at work, my new official title is Eng 2, which is hilariously generic, but still quite nice.
  • I got a working Makefile style bootstrap for the Core Jacket System's brain, even though I hit a few weird roadblocks that I'm going to have to get around. Worthy of a blog post in and of itself.
  • I've been working on moving away from evil-mode. More on that in another blog post, too

Time Spent by the Numbers

This week, I tracked 52:56 of 168 hours, which is just over 30% of my time logged. That includes the time I've spent so far on working on this post.

Of the time tracked:

7:30 Sleep 4.46
6:53 General Organizational State 4.10
6:49 Reading internets 4.06
3:37 tasks related to Body computing System 2.15
2:16 Lunch 1.35
1:37 Habit Forming and Management 0.96
0:18 tasks related to Freestyle Emacs and Tooling stuff 0.18
29.00 All Time Tracked Time%
5:45 General Time Spent 3.42
5:21 tasks related to Datacenter Failover strategies 3.18
4:17 Scheduled Meetings 2.55
3:07 tasks related to monitor and on-call training 1.86
2:10 Unscheduled Meetings 1.29
1:43 tasks related to internal Node.js packages 1.02
0:34 Checking Email1 0.34
0:59 tasks related to Release Process 0.59
23.93 Work Time Tracked Time%

Of note:

  • Tracking my sleep time manually is bordering on useless; I should use the data that I collect via Sleep as Android and process it via Memacs or so.
  • I need to make sure that unscheduled meetings are handled a little bit nicer; my work is interrupt-driven by nature but things like these I should be able to cut down on.
  • General Organization State is something that I need to force myself out of; it's the default state set by bh/org-clock-in-organization-task-as-default which is bound to F9 i, so it's often the state I get stuck in when I'm not working on anything, or when I complete a non-project task.
  • Breaking this down by project may not be a good way to lay out these times, or I may be misorganizing things; for example, I rebuilt my devserver which is cataloged under tasks related to internal Node.js packages, but should probably be in its own tree
  • The last week has felt way more hectic than these charts have really let on; a bunch of outages and interrupts, as well as having to deal with the fallout from a pretty serious outage last week, left me feeling like I got way less than I wanted to get done this week. Need to catalog those better so that I at least can feel like I didn't waste a bunch of time this week.
  • I lost a day this week, feeling completely and totally out of it because of the fact that I've been fighting the flu/bronchitis plague that's gone around my office and friends circle. It's where most of my Reading internets went. I should just be honest about days like that and take them as actual rest so that my team can organize without me instead of around me.

Interesting things I learned or read

Looking Ahead

I have been working on updating internal Node 0.10 projects to npm2 and making steady headway on getting iojs 1.4 in to production. Next week I'd like to make headway on that, even though I'm planning to push off the hard deadline that I pushed.


  • Land npm2 support for our main codebase and its dependencies
  • Clean out last of our datacenter outage work
  • Hold an on-call training session
  • Update and prune the on-call rotations that I am responsible for
  • Prepare for week-off
    • Get prio1 tasks done
    • Hand off everything else


  • Create plan for my time off
    • Server migration strategy
    • Make appointments:
      • General Doctor
      • Vision
      • Dentist
      • Tax accountant
  • Get a pair of rollerblades
  • Get my chromebook to the point where I can use it without my work laptop at home and blog about it
  • Look at getting the Tf700 in to the same state
  • Open a maintenance ticket to fix my blinds
  • Work on Inventory
    • Finish moving the e-book part of my inventory2
    • Fill out all of the small crates
  • Get GSM modem working on the Core Jacket System's pi brain
    • Look at writing an nmcli ansible module
  • If that's easy enough, look at getting hostapd put together
  • Set up Hydra, complete moving evil-mode out of my non prog-mode buffers. This is worth a blog post



I think a lot of this falls in to Organization state, which I need to be sure that I spend less time in since it's a black box.


More on this later; I'm archiving everything of value that I own, in short, including digital assets like that.