diff --git a/9db45ab6.html b/9db45ab6.html index 2ee7e8a..d6324b0 100644 --- a/9db45ab6.html +++ b/9db45ab6.html @@ -63,4 +63,4 @@ code span.st { color: #4e9a06; } /* String */ code span.va { color: #000000; } /* Variable */ code span.vs { color: #4e9a06; } /* VerbatimString */ code span.wa { color: #8f5902; font-weight: bold; font-style: italic; } /* Warning */ -

focus requires a rigorous contract

Balancing many disparate tasks is good for my morale (“Wow! If I get bored with this one thing, I can just do something else!”), but feeling “behind” is most decidedly not good for my morale. Timeblocking and scheduling are great, but they require discipline. I like to think that I am effectively entering into a short-term contract with myself. If the terms aren’t clear, the chances of failure go up (significantly). Interestingly, I think this scenario represents a conflict of interest: I am basically the party responsible for monitoring that contract, as well as the one actually executing the work.

Besides having a clear plan (a statement of work) I think the next biggest concern involves distractions. In my experience, you can’t get rid of distractions, but you can be judicious about what distractions you choose to entertain. That gets to the same end-goal of choosing when to focus on distractions, but puts a different emphasis on the problem.

The “hard” part (to me) is that developing the intuition of what to do (and when) is much easier said than done. Maybe because it is a constantly moving target?

logo
\ No newline at end of file +

focus requires a rigorous contract

Balancing many disparate tasks is good for my morale (“Wow! If I get bored with this one thing, I can just do something else!”), but feeling “behind” is most decidedly not good for my morale. Timeblocking and scheduling are great, but they require discipline. I like to think that I am effectively entering into a short-term contract with myself. If the terms aren’t clear, the chances of failure go up (significantly). Interestingly, I think this scenario represents a conflict of interest: I am basically the party responsible for monitoring that contract, as well as the one actually executing the work.

Besides having a clear plan (a statement of work) I think the next biggest concern involves distractions. In my experience, you can’t get rid of distractions, but you can be judicious about what distractions you choose to entertain. That gets to the same end-goal of choosing when to focus on distractions, but puts a different emphasis on the problem.

The “hard” part (to me) is that developing the intuition of what to do (and when) is much easier said than done. Maybe because it is a constantly moving target?

logo
\ No newline at end of file diff --git a/acc60422.html b/acc60422.html index a10bdc2..33081d1 100644 --- a/acc60422.html +++ b/acc60422.html @@ -60,4 +60,4 @@ code span.st { color: #4e9a06; } /* String */ code span.va { color: #000000; } /* Variable */ code span.vs { color: #4e9a06; } /* VerbatimString */ code span.wa { color: #8f5902; font-weight: bold; font-style: italic; } /* Warning */ -
logo
\ No newline at end of file +
logo
\ No newline at end of file diff --git a/c4e96daf.html b/c4e96daf.html index 3a71d71..772c9c0 100644 --- a/c4e96daf.html +++ b/c4e96daf.html @@ -60,9 +60,9 @@ code span.va { color: #000000; } /* Variable */ code span.vs { color: #4e9a06; } /* VerbatimString */ code span.wa { color: #8f5902; font-weight: bold; font-style: italic; } /* Warning */

adding a new user account on a linux system

adduser $USER
-usermod -aG sudo $USER
+usermod -aG sudo $USER
 # if account requires password-less elevation:
-sudo visudo  # add an entry like: $USER ALL=(ALL) NOPASSWD:ALL
+sudo visudo  # add an entry like: $USER ALL=(ALL) NOPASSWD:ALL
 # confirm that the account works as expected
-su - $USER
+su - $USER
logo
\ No newline at end of file diff --git a/dc879f80.html b/dc879f80.html new file mode 100644 index 0000000..3f43fc5 --- /dev/null +++ b/dc879f80.html @@ -0,0 +1,64 @@ +how i stay (somewhat) organized - zettel.thermokar.st

how i stay (somewhat) organized

Right now this is just a draft outline, ideally I will circle back on this some time this year to fill in some more details.

  • Tools
    • Notebook
      • Right now this is actually just half-letter-page (5.5 inches × 8.5 inches) sheets on a similarly sized clipboard + pen.
      • Pre-printed time block pages: four columns (for amending schedule) + twenty-two 30min rows.
      • Blank pages for logging daily notes, observations, and ideas.
        • I use some elements of bullet journaling for this:
          • I love the bullet syntax, so I use that often (and a homegrown shorthand).
          • I migrate tasks from page to page, but don’t follow any of the weekly/monthly/yearly migrations.
          • The second or third time a task is migrated, I move this task over to my digital planner app (more below).
          • Reflection happens ideally once a day, but more like 2 or 3 times a week.
      • Periodically I clear out the clipboard to archive older sheets that I won’t need to update - these get scanned and put into a per-annum PDF document that is synced to my phone and computer.
    • Calendar
      • I check my digital calendar multiple times a day: I use this to communicate shared calendar events with team members, as well as personal events, deadlines, etc.
    • Home-grown todoist clone
      • repo: git://pingo.thermokar.st/planner
      • live: https://planner.thermokar.st (access restricted)
      • Structure
        • This planner is modeled after GTD practices and features an inbox, and the ability to categorize tasks into one or more “plans” (plans can be a project, a specific day/week/events todo list, an issue tracker, etc).
  • Routines
    • Daily
      • I triage notifications first thing in the morning (no more than 30 mins),
        • Note, I might move away from this: I would prefer to handle that kind of stuff midday if possible.
      • Timeblock the day’s schedule (see: focus requires a rigorous contract), incorporating prior engagements, any urgent ad hoc tasks, and the week’s goals (more below).
        • If I fall behind or something unexpected comes up, I update the timeblock schedule when I get a chance.
      • Weekly
        • Before each week starts I try to identify a few high-level goals for the week, and figure out (broadly) how they might fit into my schedule, but I don’t worry too much about specific scheduling at this point, just something like “Wednesday would be a good day to carve out time for this…”
      • Long-term
        • My calendar handles big things like major work milestones, deadlines, appointments, meetings, etc.
        • Tasks go into my planner app, I review these 3-5 times a month on average to see how they might fit into what is coming up next, etc. Really long-term tasks get filed into an @someday plan.
logo
\ No newline at end of file diff --git a/index.html b/index.html index 17f071a..4c4844b 100644 --- a/index.html +++ b/index.html @@ -60,4 +60,4 @@ code span.st { color: #4e9a06; } /* String */ code span.va { color: #000000; } /* Variable */ code span.vs { color: #4e9a06; } /* VerbatimString */ code span.wa { color: #8f5902; font-weight: bold; font-style: italic; } /* Warning */ -
logo
\ No newline at end of file +
logo
\ No newline at end of file diff --git a/search.html b/search.html index ea87739..c283d0a 100644 --- a/search.html +++ b/search.html @@ -1,4 +1,4 @@ -Search - zettel.thermokar.st

Search

Search

    logo
    \ No newline at end of file +
    logo
    \ No newline at end of file diff --git a/z-index.html b/z-index.html index 298af08..6270fbc 100644 --- a/z-index.html +++ b/z-index.html @@ -59,4 +59,4 @@ code span.st { color: #4e9a06; } /* String */ code span.va { color: #000000; } /* Variable */ code span.vs { color: #4e9a06; } /* VerbatimString */ code span.wa { color: #8f5902; font-weight: bold; font-style: italic; } /* Warning */ -

    Zettel Index

    Notes without any folgezettel relationships

    The zettelkasten has 9 zettels and 10 links. It has 2 clusters in its folgezettel graph. Each cluster's folgezettel heterarchy is rendered as a forest.

    logo
    \ No newline at end of file +

    Zettel Index

    Notes without any folgezettel relationships

    The zettelkasten has 10 zettels and 13 links. It has 2 clusters in its folgezettel graph. Each cluster's folgezettel heterarchy is rendered as a forest.

    logo
    \ No newline at end of file