Young Hands Club

February 10, 2020

JFW plan, week of 10 Feb 2020

Filed under: Jacob Welsh — Jacob Welsh @ 6:22 am

Daily template

Morning (6h):

  • 0.5h warmup
  • 2h log + blog reading + responses, or errands
  • 0.5h breakfast
  • 1h reading: alternating days of discretionary vs. work and forum-related ((Half an hour at a time was just a tease and I didn’t once manage to stay in the limit.))
  • 2h write for blog + break
  • 0.5h flex

Afternoon (5h):

  • 0.5h lunch
  • 2pm – 4:30pm project work + #o chat window
  • 1.5h focused project work time
  • .5h walk or exercise (start by 6pm)

Evening (5h):

  • 2h dinner
  • 1.5h flex
  • 0.5h blog prep
  • 0.5h journal
  • 0.5h winding down

This indicates 4-6 hours for project work on typical days. Subtracting 4 for weekly review and planning and 4-6 for social time gives 18-34 in the week.

Project tasks

1. Prepare for presentations: 15h

2. gbw signer development: 5h (time permitting)

3. musl outreach suggested by MP. I haven’t committed to anything yet but time is a factor; would need to better figure out what’s involved. (time permitting)

4. Ask questions about proposed V and clearsigning changes. I spent some time trying to make sense of that discussion, making some headway but questions remain both philosophical and technical. Thinking to test the waters first in #o. (time permitting)

Other notes

The conference is on Thursday and Friday covering much of the work day. I’m guessing I won’t manage any blog writing those days.

My sleep cycle advanced about 1.5h last week; I’ll stick to the gradual ratchet.

JFW review, week of 3 Feb 2020

Filed under: Jacob Welsh — Jacob Welsh @ 6:04 am

A big question in the background this week was my Master’s about identifying or choosing my own top priority. I haven’t come much closer to an answer.

On the positive side, my #trilema log catchup went fine and finished well under the cautious time estimate. There’s still one or two of the threads I identified there to follow up on as time permits. I picked up steam again on wallet development, getting in just over the planned 10 hours. I’ve completed what’s probably the toughest part, the transaction signing mechanism, to my standards of code quality (though it will need a fresh re-read at least, and some surrounding pieces are still needed to able to test it). This took well over the December work plan’s two-hour estimate, in part because I’d missed considering some of the necessary parts there (transaction binary encoding). But it’s in a good state to pause for now and pick back up after my presentations are squared away, and still on target for my February 21 ETA.

The new plan structure worked out somewhat, for example getting me to allow myself some pleasure reading, which I put toward M. Luby’s paper on the theoretical level of his LT code scheme (okay, perhaps I have an odd sense of pleasure). It tended to fall apart towards the end of the day as many things would run over not just their own time but the carefully placed buffers. I’m still seeing substantial unplanned time spent on reading articles or pondering, when I’m supposed to work on projects or writing. Better than doing nothing I suppose but I still need to improve at focusing on the task at hand.

Blogging was a particular pain point; after getting stuck on the last log summary article Monday, I didn’t give it the time on Tuesday, then did spend time but to no avail on Wednesday. At that point I switched to the long-planned photo series which got the pen moving again, though at a snail’s pace (and not at all this weekend). I also avoided speaking up about this as it transpired.

I also had trouble getting started with the presentations, and at the end of the week appealed to Robinson to help on the idea of the more sales-oriented approach. We worked through that at the high level today which I found quite helpful.

February 3, 2020

JFW review, week of Jan 27 2020

Filed under: Jacob Welsh — Jacob Welsh @ 6:13 am

I acted rather impulsively this week, and even saw it happening and felt some guilty pleasure in it. It’s not that I did anything outright harmful, but I went far off the plan at the expense of my own priorities. I’m also seeing it as illustrating my Master’s point about relativity of dislike for tasks, just not applying it to my own benefit, as well as my old standby the “avoidance by hard work”.

The main examples coming to mind are: leaving some lengthy comments; reading quite a few articles; and a big one I found myself reluctant to admit: starting on some coding to scratch an old itch of wanting a more streamlined and automated personal web archiving process. The trigger for this was perhaps having learned that Eric’s existing thing wasn’t quite what I was after.

Casualties included wallet development, and presentation prep where I only got 3 of the planned 10 hours (not counting the chat).

I’m relieved to have paid down some debts, chiefly my #trilema backlog (or most of it) and wayward weekly reviews, though I missed my Saturday deadline for this one. I published four blog articles, missing three days; at least this maintained the output level of the previous week. My journal suffered though, seeing only two entries at the start of the week.

On Saturday evening Robinson and I joined our friend to resume our Unix and management training exchanges, which was productive and enjoyable.

JFW plan, week of Feb 3 2020

Filed under: Jacob Welsh — Jacob Welsh @ 6:01 am

This week I’m trying a new plan format, in search of improved balance in providing enough guidance to keep me on track and attending to the things I say are important yet enough flexibility to accommodate the surprises of both the outside and inside world.

Daily template

Morning (6h):

  • 0.5h warmup
  • 0.5h pleasure reading
  • 2h log + blog reading + responses, or errands
  • 0.5h breakfast
  • 2h write for blog + break
  • 0.5h flex

Afternoon (5h):

  • 0.5h lunch
  • 1.5h focused project work time
  • Starting 2pm: 2.5h project work + #o chat window
  • 0.5h walk or exercise

Evening (5h):

  • 2h dinner
  • 1.5h flex
  • 0.5h blog prep
  • 0.5h pleasure writing (journal)
  • 0.5h winding down

This indicates 4-6 hours for project work on typical days. Subtracting 4 for weekly review and planning and 4-6 for social time gives 18-34 in the week. (No wonder 40-hour saltmining doesn’t leave space for much else, huh.)

Required project tasks

1. #trilema catchup: 8h (not sure how much is left so I’m aiming for a high estimate; I believe there’s about a week where I’m filling in gaps from partial reading, after which I followed fully.)

2. Review feedback and prepare for Feb 13 + 14 presentations: 10h (someone else stepped up for Junto the 12th so I’m off that hook for now.)

3. gbw signer development: 10h

Other notes

Same plan as last week for gradual adjustment of sleep cycle, as the late Tuesday night threw off the last try.

January 29, 2020

JFW review, week of Jan 20 2019

Filed under: Jacob Welsh — Jacob Welsh @ 8:06 am

Last week I finally got started on my #trilema backlog, working through nine days of log in three of reading, with an article published for each of the three. The plan, though, was to do some every day and be finished by now. The summarizing was rough on the first try, focusing too closely then not making it through even after overflowing the target time, but picked up after my Master’s advice to take it easier and work more from memory.

A Monday article completing the draft gbw-node series brought the total publication count to four, leaving Tuesday, Wednesday and Sunday dry. The trouble Wednesday was not having thought through the photo blogging enough to plan time to sort through the stack. (This was the case too for my earlier photo articles, just less noticeable as the stacks were smaller.) So the vacation article has had to wait.

Tuesday was a low point in productivity at least relative to plan, as I got none of the intended tasks done. Instead there was a fair amount of reading, some chat and blog comments, 0.75 hours explicitly noted as stupidity worship, and an early bedtime. Perhaps I needed a break, but from what I’m not certain; perhaps the heavier writing of the four prior days.

The wallet work, which my Master had figured should be the top priority, also suffered, getting only four hours of the planned 10, between Monday and Wednesday. Within that time though it moved well.

I was a better friend to my journal than weeks before, writing five entries.

I figured I’d have to set myself up properly to get the two reviews done, but come Saturday the schedule was looking tight. I almost passed on an invite for pizza and drinks at a new pub that evening, but once I got my article out I figured I’d go, just keep it brief and get the first review in before bed. But the conversations started to get interesting, and while I didn’t stay terribly late, the “brief” didn’t end up quite brief enough. On Sunday morning I scrutinized my time log from earlier Saturday, wondering why I’d started the “actual work” so late, even accounting for a grocery run. The main thing I found was unplanned time spent on current #t log reading and processing (MP had given detailed responses to Robinson and me). Since that surely could have waited a day or two, I suppose my root problem is still a lack of firmly reserved minimum time blocks for the critical tasks. Then that pattern basically repeated on Sunday, to where I ended up hoping to somehow squeeze both reviews in. The week provided plenty of reminders that time doesn’t just appear “later” because you’d like it to.

Some selections from the log:

jfw: I find I was not very productive yesterday. While I got a fair amount of reading in, I believe I used this in part as avoidance of getting started on writing; then there was stupidity worshipping in the same vein; and snowballing by not wanting to admit failure there thus not getting to other priorities either.
diana_coman: jfw: heh, one way to make all that avoidance work for you is to set it up explicitly (need to do task A you hate? cool, set up task B that you hate even more!)
jfw: http://logs.ossasepia.com/log/ossasepia/2020-01-22#1015800 – I have my doubts but maybe I’ll try it some time.
diana_coman: http://logs.ossasepia.com/log/ossasepia/2020-01-22#1015809 – what doubts exactly? spell them out, maybe there is something to them or maybe it highlights a different trouble.
jfw: diana_coman: trying to spell out that doubt then – I would not be “fooled” by setting up task B: I’d know it’s a ploy to make task A seem more attractive by comparison; or if I did see B as truly urgent, I’d end up all the more glum for having both on the plate but not touch A because B was more important.
diana_coman: jfw: hm, you don’t seem to quite get the idea though: it’s not even meant to “fool”, no, and it’s not about more important either.
diana_coman: http://logs.ossasepia.com/log/ossasepia/2020-01-23#1015837 – to flesh this out some more: dragging your feet on getting started on something is still a signal (others call it at times laziness, plenty of ways to call it too)
diana_coman: if you interpreted that as simply “I hate what I need to do for this”
diana_coman: rather than “I need to sort out something else first in order to be able to start on this”
diana_coman: then the answer to that is a straightforward escalation without any pretense
diana_coman: perceptions/projections of the sort “I don’t like it” are relative, there’s no escape to that part
diana_coman: hence the if you don’t like that, here’s worse so that you’ll like it
diana_coman: it is true however that the above will work *only* if you interpreted the signal correctly in the first place
diana_coman: so indeed if you got that initial part wrong, then the problem is different and therefore the solution to it will be different too
diana_coman: jfw: hence, it’s worth indeed to have first another open minded look at the signal, sure; so – what is it you got stuck on?
diana_coman: (re “ploy” and all that, note that there’s no fooling, just using the existing mechanism quite on purpose; if you want a practical example of that, do that simple experiment with temperature: get some water at room temperature, some hotter and some colder; keep for a while one hand in the cold water, one in the hotter; then put both (one at a time for less confusing direct reading) in the room temperature water and see how one …
diana_coman: … reports it “cold” and the other “warm” – while you even know why and how and everything, did the hands get “fooled” or not? the perception is what it is and gets reported as such regardless of what higher-level thinking says)
diana_coman: the above could be again restated as the older “get over yourself”, sure, but I think it’s way better to get *on with* yourself simply.

dorion: http://logs.ossasepia.com/log/ossasepia/2020-01-23#1015845 – part of his strong arm is seeing negatives/mitigating risks – doesn’t mean he hasn’t helped me see positives where I was focusing on negatives – but sometimes he expects from his weak arm feats his strong arm can do.
diana_coman: http://logs.ossasepia.com/log/ossasepia/2020-01-23#1015858 – linked at the root with not being all that comfortable with handling uncertainty

diana_coman: jfw: did you count in there the fact that “trying to do all those” is currently yet-another-something-new and therefore a *task* in itself that you are taking on?
jfw: hah, I suppose not

diana_coman: jfw: btw, from the sounds of it, what makes you avoid/postpone/drag your feet there is not perceived difficulty but outright perfectionism getting in the way.

jfw: diana_coman: I was pleased with the improvement in the article quality dimension, unfortunately the time wastage did not improve. I find I engaged in various other chats first, which surely could have waited a bit longer, then once started I let it drag on about 3 hours. I recall this being mostly pondering & obsessing & some re-reading & outlining at first, then once I got moving it wasn’t so bad.
jfw: This then came at the expense of the wallet work time.
diana_coman: jfw: yeah, you need to learn to just get moving; time for pondering is when you go for a walk/set aside time specifically/can’t do anything else anyway, that sort of thing but not when you should just start on something; takes some practice though, like everything else.

January 27, 2020

JFW plan, week of Jan 27 2020

Filed under: Jacob Welsh — Jacob Welsh @ 6:16 am

1. Upcoming

I will have three talks to give on Feb. 12-14: first for the Junto on Relational Database Management (pushed back from this week), and two for a private conference being put on by our clients, my tentative topics “There ain’t no such thing as a free block” and “Low-tech entropy and everyday digital hygiene”. The last of those will be based on one I’ve done before but all will require preparation over the coming 2.5 weeks.

2. Required tasks

1. Last week’s missed review: 3h, deadline Tuesday

2. #trilema catchup: 2h daily

3. Blogging: .5h planning (when needed, doesn’t seem so for the log summaries) + 1.5h writing daily (possible topics: continuing #t log summaries; trip photos; thoughts on family)

4. gbw signer development: 4h, aiming for Monday

5. Preparing for talks: 6h

6. Forum interaction + misc. reading: 1-2h/day

7. Weekly review + plan: 4h, deadline 4pm local / 9pm UTC Saturday (because otherwise it just doesn’t seem to move!)

8. End-of-day journal: .5h/day

3. Other

Sleep schedule has not improved as much as desired. What worked last time was writing out a schedule of bedtimes + corresponding target waking and meal times so I’d stay on track; I’ll try doing that again.

JFW review, week of Dec 16 2019

Filed under: Jacob Welsh — Jacob Welsh @ 4:25 am

That’s right: in this review I’ll be reaching all the way back to the misty, primordial ages of 2019 to fill in a missing link in the chain of reflections.

I published two Fixpoint articles, beginning my series presenting code, commentary and rationale for my draft Gales Bitcoin Wallet, covering the SQL schema Monday and starting on the Python data-wrangling part Tuesday. I took the opportunity to ingest the entire documentation of both languages into the Fixpoint reference library to head off the expected upstream decay. MP heartily endorsed the point about the advantage of a relational database for decoupling program and data and offered initial thoughts on the SQLite choice.

These articles ate up a whopping 5.9 and 8 hours each, compared to the budgeted ~2h daily, which certainly upset the remaining schedule. It doesn’t look like I communicated much about this as it was unfolding. Another problem with the plan was just being too packed; extrapolating the hours even just to five days would give a 57-hour work week.

Dropped items from the plan were #2 (Uruguay expense roundup, which I completed on the trip), arguably #6 (forum reading and interaction: I got in a good amount but probably not 3h/day), #7 (weekly review and next plan), a Wednesday article, and #9 (offline wallet dev). I also didn’t get much (any?) sleep Wednesday night prior to Thursday morning departure, but was able to make up a bit on the plane.

Packing fit a bit under the planned 3 hours and I didn’t miss anything so I figure that was fine. I got my #trilema responses out, though not by my own Monday deadline. The keksum re-genesis was fine though without a minute to spare to notice the damage to the article title.

Tuesday Diana Coman asked how I was planning to handle the work to holiday transition, outlining the three options. I took some time to record the wallet work in-flight; combined with the several existing spec and planning articles I didn’t have much trouble picking it back up in January. (More trouble on that front seems to have been with my writing and planning and generally getting back into a work mode.) She also called out my repeated not-quite-asked-questions, something I believe I’ve since kept well in mind and improved at including in conversations with others. On Wednesday I had some seriously optimistic ideas about how available I’d be over the holiday, which she adjusted to a more realistic level (except that even the “I’ll at least try to read logs” didn’t end up doing much).

January 20, 2020

JFW plan, week of Jan 20 2020

Filed under: Jacob Welsh — Jacob Welsh @ 6:04 am

Required Tasks

1. #trilema catchup: 2h daily, ETA end of the week

2. Blogging: .5h planning + 1.5h writing daily (planned topics: some mixture of finishing gbw-node draft writeups; return to family topics; trip photos; #t logs)

3. gbw signer development: 10h

4. Forum interaction + misc. reading: 1-2h/day

5. Weekly review + plan (still including that missed December week!): 5h (still aiming to do Saturday!)

6. End-of-day journal: .5h/day

JFW review, week of Jan 13 2020

Filed under: Jacob Welsh — Jacob Welsh @ 5:54 am

Somehow, getting moving on this week’s review has been even more fitful than usual. I keep planning to do them on Saturdays; of course this requires choosing to do it at the expense of something else at that time, and there’s never a shortage of easier (or at least more comfortable) yet still important things to get done at every juncture up until deferring is no longer possible. It also requires enforcing my own deadline and working well rather than worshiping stupidity so as not to lose time on Saturday AND still have to finish on Sunday, and perhaps I’m not yet confident enough in my ability to do that without the external pressure.

Of course I have nothing to lose from looking honestly at the week. I spoke up about my failings… well not always, but then spoke up about that too:

jfw: ahoy, I’ve again failed to get my article written; I did make good headway on organizing my loose pile of thoughts on the family, so I won’t consider the time a waste.
jfw: I’ve noticed that one time-stretching self-delusion I’m prone to is “I haven’t yet sat down and logged a start time on task X, thus I’m now ‘preparing myself’ or something and can drag feet and it totally doesn’t count as time spent on X

jfw: I’ve made slow headway on the drafting, but I’m falling on face again as far as getting it done. whaack’s arriving momentarily. Will get back to it either tonight or more likely first thing tomorrow.

jfw: diana_coman: another day of failure to publish here. Seeing the spinning and wondering why I couldn’t stop, I turned to writing whatever thoughts, which turned into a kind of internal dialogue. If I’m not willing to put forward my thoughts as truth, I can at least posit and consider them

jfw: I also let myself get worked up / stressed yesterday from being again behind on my plan. And hesitated to speak up along the way because of… perhaps some shame at how slow things were going plus a vain hope that I’d somehow still get it all in.
jfw: Specifically – I’m not getting my 5 hours of wallet dev, and while I caught up on the #o log from break and got assorted blog reading in, I’ve barely made a dent in a mountain of #t backlog

Indeed this did not get me eaten; rather I received helpful feedback and course adjustments. Once back on the technical series I got four articles out with minimal fuss.

Further positives included getting out some blog responses on Gales Linux, completing training session delivery for our twice-weekly pilot clients, and spending two quality evenings with Will.

A regression was not keeping up with the daily journal. I had put it under “time permitting”, figuring I had a lot on the plate, and naturally time didn’t permit of its own accord. I’d like to get back to that and perhaps also use that time for closer examination of my time logs to get more value out of them.

January 13, 2020

JFW plan, week of Jan 13 2020

Filed under: Jacob Welsh — Jacob Welsh @ 6:05 am

Required tasks

1. Catch up on recent logs and blogs: 15h (last ETA I gave was Tuesday and I will push for this). ETA Tuesday for #ossasepia, Friday for #trilema.

2. Meeting Will; attending Junto: 4h (Tuesday+Wednesday evening)

3. Training development + delivery: 5h on Thursday (overflowed final session of the pilot run).

4. gbw signer (offline wallet) development: 5h (planning increase to 10 going forward)

5. Daily blogging (topics include finishing “what’s on my mind”, continuing gbw-node code writeup series, though maybe vacation photos first): 14h

6. Daily forum interaction: 10h total, 1-3h/day

7. Weekly review and plan: 4h5h including the missed December week, aim to finish by Saturday.

Time permitting

8. Blog: thoughts on how V-based OS might work.

9. End-of-day journalling: 3h.

« Newer PostsOlder Posts »

Work on what matters, so you matter too.