Weekend Only Goals

[zedmango]

@dreev

even though you’re accurately measuring “days I did everything I needed to” that’s not as useful and interesting a graph as one showing “number of actual things I did” over time.

See, I find it a lot more useful to know whether I did what I needed to.

I think this is related to Team Yellow vs. Team Black:

Team Black vs Team Yellow: The Two Styles of Beeminding

Those of us on Team Black, like me, care about the logging system being most motivating, not the purity of the real-world nature of the graph. This way, the data you log is a function of both what you do and what you need to do, as opposed to just what you do.

What do you think is the best way to handle weekend-only goals?

Another possibility is to allow for uploading a list of numbers used to shape your future road - that way you could script something that would create a table to auto-modify your road for weekend-only the way @apolyton does manually.

Here’s another example:

Beeminding a specific craft project

How about the following: Have a slope of 1. Every day, if you don’t have a motif to make and are in a beemergency, add a datapoint of 1. (Think of this as “all caught up for today.”) Use IFTTT to add a 3 datapoint whenever you enter a datapoint on your reading goal. Now you’re caught up for 3 days but you can’t enter a datapoint until you make the motif.