This is my 2nd or 3rd attempt at calendialish journalling. Intentionally cryptic motivation: I found reason to reevaluate whether to adjust my relationship with Beeminder. This thread will serve that purpose, I hope!
I feel like can go through next week just not derailing… but I at least want to have some more breathing room after that.
p.s. visual graph editor keeps hanging… I initially wanted to keep the goal date and total fixed, so that I’d be reminded of the impact of this change. But well, here’s the configuration pre this change. Goal date: 2026-11-22 / Total: 150 / Daily slope: 0.41209
I’m really happy with the earlier changes. I’ve managed to get both of the goals into safe territory before I traveled abroad.
Beebudget reports my running goal as the highest loading goal. I have my running gear with me as I’m away from home, I’ll be back home in 9 days, and otherwise I’m happy with the rate. So no changes.
Side note on beebudget and the playbook of this topic
When I made beebudget, I wanted to try out the idea quickly. It uses the goal configuration (which I believe means the last segment of the red line). Now that I’m using Beeminder in a slightly different way, this isn’t working well for me anymore. Until the next calendialing, I may fix that, or complicate the playbook to account for this.
This is the lowest level Computer Science material I’ve ever studied besides a introduction to computing course I took about 15 years ago. I find it mildly interesting and fun.
After ~13 hours and 1 derailment (a silly 5$ one, due to New Year’s Eve), a few things are clear to me:
I don’t want to be pushed so much to stick to this.
I don’t have an important reason to finish studying this in a year.
I don’t want to invest equally into studying SICP and CS:APP.
So I’m dialing this goal down:
Keeping the goal of studying 150 hours fixed, I moved the goal date to 2027-12-01.
This brings down the daily slope to about 12 minutes.