|
|
|
|
|
by hawkice
3383 days ago
|
|
I just meant, that, not only is the premise of commitment contracts well thought through, the smaller choices, like the 1 week delay on changing a goal setting, to why the exponential increase in punishments is closer to tripling than doubling, are all thought through and justified on the blog and have been clearly tweaked over time. You guys even have super transparency, and iirc mention you provide it because commitment contracts would incentive you to encourage failure, and that's not what you want at all. Compare that against e.g. Trello, which is good looking and usable, but it's kanban without queue limiting. That defeats the whole point! (I explain this in more detail here: https://gen517.com/queue-limiting-the-whole-point-of-kanban/ ) The difference between trello and beeminder (to me, at least) is that the beeminder people think about how to provide anti-akratic tools a lot, and embed their thoughts and discoveries into their product. The Trello people basically provide nice CSS for a tool so flexible it has nothing to say at all. If I want digital paper, sure, Trello is nice. If I want _actual help with something_? I'd prefer software developed by people trying to help me. |
|
And really excellent point about queue limiting and kanban! Now I'm wondering if there's a hack or plugin or just a convention to make Trello work that way...
Or maybe the answer is Beeminder's Trello integration, to enforce limits on Trello cards. :)