Required tasks
Training development + delivery: 15h (final two sessions of the pilot run).
Catch up on recent logs and blogs + engage as necessary: 25h (2-5h per day).
Continue gbw-node code writeup series: 10h.
Weekly review (which really should also cover the last short week I missed doing one) and plan: 4h, aim to finish by Saturday. I’m thinking to try some end-of-day journalling to see if this makes the end-of-week reviewing less daunting.
Time permitting
Blog topics: vacation photos; thoughts on how V-based OS might work.
gbw signer (offline wallet) development.
The end-of-day journalling sounds like a good idea. What’s the status/plan/current agreement re delivery re wallet though?
Comment by Diana Coman — January 6, 2020 @ 8:02 am
We’ll be clarifying client preferences later today; in any event Robinson and I still see it as a fairly high priority. Trying to take a more realistic view, looking at the last plan and giving another clueless-estimation factor of 2x for remaining tasks gives 52 hours, or 40 if documentation beyond what I’m already doing on the blog proves unnecessary. In the latter case, if I can give it 15 hours a week starting next week, it could be done this month.
Comment by Jacob Welsh — January 7, 2020 @ 6:54 pm
Clients are fine with having the wallet done by end of first quarter, so reducing it to 5-10 hours a week is looking like an option.
Comment by Jacob Welsh — January 8, 2020 @ 4:59 am
Sounds good. I’d still keep it around 10 or 10+ though, since the earlier it’s done the better anyway and otherwise that still leaves you with reasonable time for other stuff as far as I understand it.
Comment by Diana Coman — January 8, 2020 @ 7:37 am
[…] block/spinning/phobia/whatever was back in force this week, and I allowed this to mess up my other plans. In this moment I find myself glum about it: “couldn’t I have picked a path that didn’t need this? […]
Pingback by JFW review, week of Jan 6 2020 « Young Hands Club — January 13, 2020 @ 5:47 am