Note that the date window in the title is now only seven days inclusive, down from eight. ((i.e. Last week’s plan was Nov 11th – Nov 18th)) This small detail is meant to represent a new era of my time management where I do not consider Sunday night an opportunity to finish leftover work for the week. In addition, per diana_coman’s advice, I will break this week’s task into daily chunks. The downside of this is that since this plan is more specific, it will need more alterations throughout the week. The upside is I am held accountable for any daily failings immediately.
Each day includes log reviewing as well as a little Spanish study, although these are not explicitly listed. Surfing and guitar are snipped out and are just treated as a reward upon completion of a good day of work.
1. Monday 11/18
- Saltmines (8h) ((Only did 4))
2. Tuesday 11/19
- Travel to nearby town to pickup chair ((Mugui won’t deliver my chair to the door, and they don’t have an office. They gave me the personal number of the delivery guy, and I have to meet him on the road in a nearby county.))
- Saltmines (8h)
3. Wednesday 11/20
- Read the man page of rsync and fix crontask so blog gets backed up locally. Write a sane backup strategy with corresponding scripts. (4h)
The script that backs up the blog will contain an if-external-hard-drive-plugged-in-save-it-there-too clause. The script will also keep a saved copy of the wget of all younghands posts.(2hr) Saltmines (8h)Make the worthless pathfinder someone else’s problem (2h)Surfpal doesn’t seem to care about moving the car, perhaps because he understands its actual value. ((I told surfpal I will fill it up with gas and drop it off where he likes. He hasn’t followed up with me and if he doesn’t I will focus on taking care of other shit first. But I would like to get it out of the way.))Finish rough draft of first An Outpost of Progress article (2h)- Begin list of computer part accessories and items needed from the hardware store. (2h)
4. Thursday 11/21
- Continue list of computer part accessories and items needed from the hardware store. (3h)
- Make a trip to town. This includes grocery shopping, getting a cheap phone for backup internet via hotspotting, picking up test item from boxcorreos, and going to the hardware store. (5h)
Finish my first An Outpost of Progress article (3h)
5. Friday 11/22
- Order computer parts or plan trip to San Jose (4h)
Read 40 pages of The Odyssey and read while taking notes on the two trilema articles. recommended by diana_coman (4h)- Saltmines (4h)
6. Saturday 11/23
- Write the week’s review + plan for next week
TBD / 4 hour slot for making up a task- Saltmines (4h)
7. Sunday 11/24
- TBD / 4 hour slot for making up a task
—
“The downside of this is that since this plan is more specific, it will need more alterations throughout the week.” – that’s no downside in itself; it will get changed if/when/as needed, only make *sure* it’s for good reasons.
1.2 This is a non-plan as stated. A planned item has to be *clear*, *concrete* and *accountable”. What you have there is just a half-assed, afraid-I’ll-miss-my-surfing thing. Either you snip it out entirely from Monday since you have already 8 hours of mine work OR you set it up clearly: what exactly are you trying to advance/see done with that review?
4.2 and 4.3 with time estimates please and you’ll keep track of that and review how good your estimates were too.
5 – your focus there is weird; spending time (on anything!) is easy and a given, not worth calling it a plan like that; the plan is about what you want to get DONE and only once you state that you can add estimated time required; fix this and I mean in general, as approach.
6 and 7 what do you mean by “making up a task”?
Comment by Diana Coman — November 18, 2019 @ 5:28 pm
I removed 1.2 and made the other points more accountable and measurable tasks.
For 4.2 and 4.3 I added time estimates. I will see if my time estimates are accurate, as you say.
For your point on 5 – I see. I will not make plans that are in the vain of just ‘spend time on x’ going forward.
6 and 7 – They are extra time slots available for doing work that I had planned earlier in the week, but didn’t get done. For example, I could use the slot on Saturday for making up the 4 hours I lost today on saltmines. (Although I just added the time to Wednesday)
Also:
In the future I will itemize the list by having the numbers say 1.1, 1.2 directly under the date format in the future instead of this (1. Monday) bandaid solution I have right now.
There is another task I have that I have not put into the schedule yet. That task is dropping off the Pathfinder (that I still have after taking it back from the mechanic) with the person who is going to be trying to help surfpal sell his car.
Comment by Will Haack — November 19, 2019 @ 4:52 am
a. no more manual anything b. no more not-working anything c. proper backups d. hard-drives put to use
Added 3.1 and 4.1 + 4.2.
Removed 3.4, 4.3, and 5.2.
—
I will make some more updates to the week’s plan in the morning.
Comment by Will Haack — November 20, 2019 @ 6:46 am
3.1 No; you have and make 2 scripts, each with their own task and only ONE task to do. Don’t mix things without thinking, there are some gains to keeping those separate. So:
a. on server you’ll have a cron task backing up the db to a .sql file + making a copy of your www dir into the home dir of whatever user you have set up for rsync via ssh.
b. on local computer you have one script that does rsync via ssh on all the home dir of the user above.
c. on local computer you have another script, running at a *different time* too, that backs up your local home dir (including thus backups and whatnots but it’s *more general* ffs).
d. if you want to keep versions, you can equally have yet another local cron task at yet another time and to yet another destination (be it a 2nd external drive or just a different dir on the external backup drive) doing another rsync of the local home dir (or selected subdirs) to that.
Note that rsync can do all sorts so read and choose/set parameters properly + CHECK as in proper check, run it and look, spend some time over the next couple of days to check the backups and so on.
For one thing, you can have daily and weekly backups for instance, with the daily an exact copy (ie deleting from backup what you deleted locally too) or not and the weekly again exact snapshot at some point and so on.
Just use your brain there, as you have one. Figure out a backup *strategy* + make sure you review this from time to time too.
Comment by Diana Coman — November 20, 2019 @ 7:48 am
That backup scheme / script design makes much more sense than mine, I will follow it. I came up with that dumb design because I was tired but wanted to write a task more concrete than “make a backup script strategy.” I see the foolishness now though, especially since an open ended script design plan is equally as vague as “Create a list of computer part accessories and items needed from the hardware store.”
Comment by Will Haack — November 20, 2019 @ 4:52 pm
Updated week’s plan. Top priority is to get the backup system online. Second priority is obtaining the list of accessory items I need for my computer. Third priority, which has some crossover with the second priority, is creating a list of items I need from the hardware store.
Saltmines time planned for today was moved to Friday/Saturday to make room for top priorities. Sunday morning remains available.
Comment by Will Haack — November 20, 2019 @ 9:36 pm