Until now, I’ve used Beeminder exclusively at home, but I decided to fight
back against my tendency to slip into web surfing when I hit a hard coding
problem, by creating a goal based on my Google Chrome history.
The original idea was that I would count the number of 30 minute periods
where there was no Chrome history, and count that as one unit in beeminder.
But I changed my mind and decided to use a formula based on each interval
of no surfing (decided by the gaps between Chrome history entries), and put
that into Beeminder, but have it scaled so that 30 minutes of no-surfing
corresponds to 1 pt.
I ended up using the formula: points = minutes / 30 * log30(minutes), which
gives 1 if you put in 30 for minutes. Using x log(x) type of formula
penalizes short periods of productivity more than it rewards long periods,
which I needed, but it still makes long periods of productive work more
valuable on a marginal basis. So I think this works for me. I do exclude
crucial sites like MSDN’s c# reference from the timestamps.
What do you guys think about this idea, and is this something I could
automate using Google Chrome and Beeminder’s api?
Here’s just an example of my timestamps this morning. I will need to dial
my road quite a bit to find the best rate, that’s challenging and realistic.
8:25am - 91 min - 4.02 pts
8:36am - 11 min - 0.26 pts
8:53am - 17 min - 0.47 pts
9:55am - 62 min - 2.51 pts
10:08am - 13 min - 0.33 pts
10:54am - 46 min - 1.73 pts
10:56am - 2 min - 0.01 pts
10:58am - 2 min - 0.01 pts
10:59am - 1 min - 0 pts
11:27am - 28 min - 0.91 pts
11:36am - 9 min - 0.19 pts
Total: 10.45 pts
You received this message because you are subscribed to the Google Groups “Akratics Anonymous” group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
For more options, visit https://groups.google.com/d/optout.