Ah, yes, fractional beeminding! We talk about that at the end of blog.beeminder.com/bucket and have some notes for a longer blog post about it which I’ll paste here:
I initially thought this was too slippery a slope, that without objective criteria for what fractional amount you could log you’d gradually get weasellier and weasellier until you were entering a 0.99 for 30 seconds of work.
But I don’t think it’s as slippery as it sounds. If you try to slide down the slope you run into a wall: you keep putting in a fractional amount to eke on to the road but then soon enough the bare min is more than the fractional amount you have left. So then you have to actually finish the blog post or whatever thing you’re beeminding.
The key is the rule that you can’t get to the next integer without finishing the Thing. So you get some extra nudges with the fractional entries but you still have to hew to the overall rate.
It’s similar to having started with a longer initial flat spot, postponing the first real beemergency. In fact, the yellow brick road math says that if you’re maximally weaselly about it then allowing fractional datapoints is equivalent to “pretend I started with one more day of initial flat spot than I really did”.
So, yeah, it’s not a slippery slope you can slide down very far but the whole thing could easily become kind of pointless. Unless you could keep yourself honest with “I’m entering a 0.1 because I truly estimate I did 10% of the Thing”. Maybe worth a try?
PS: Possible annoying thing about it: you could have a beemergency where your bare min is .2 but you only have .1 left to the next integer value. So now you have to finish the Thing and do 10% of a new Thing. (Again, “Thing” is whatever unit you’re beeminding.) But, assuming you’re honest about the fractions, I guess that’s better than having to do a whole Thing on the eep day.