# Complementary Tools: Mark Forster's Final Version(s)

**URL:** <https://forum.beeminder.com/t/complementary-tools-mark-forsters-final-version-s/828>\
**Category:** Akrasia\
**Created:** [May 27, 2015, 8:57am UTC](https://forum.beeminder.com/t/complementary-tools-mark-forsters-final-version-s/828 "2015-05-27T08:57:15Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![philip](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/philip/32/1505_2.png) [@philip](https://forum.beeminder.com/u/philip)\
**Post date:** [May 27, 2015, 9:15am UTC](https://forum.beeminder.com/t/complementary-tools-mark-forsters-final-version-s/828/12 "2015-05-27T09:15:55Z")

</div>

FV and FVP behave quite differently. You may find it easier to beemind FV because the chains of selected tasks are ‘fixed’, whereas the chains in FVP are ‘fluid’. (my terms)

For beeminding FV chains, I use a copy of the [tocks script](https://github.com/dreeves/tocks) and use the comment to record the number of tasks in the chain. @dreev’s ‘count’ [aggregation method](http://forum.beeminder.com/t/documentation-of-aggregation-methods-would-be-nice/549/14) is slicker and more recent.

FVP more closely describes my actual method of working an FV list, but I haven’t yet figured out what I should beemind, because each chain may never finish, and the number of tasks in the chain isn’t known at the outset.

@drtall: FV[P] is orthogonal to beeminding pomodoros or tocks. Mark endorses doing “ **little and often** ” to make progress on a particular task, which seems perfect for having an item like “do a tock on X” in the list.

Possible proxy values:

- Clock time spent working-the-list
- Count of tasks crossed out
- Daily goals of ‘writing the list’ and ‘working the list’
- Times that I actually do cross out the top-most item

---

_[View the full topic](https://forum.beeminder.com/t/complementary-tools-mark-forsters-final-version-s/828)._