pookleblinky / lifescripts

Automating various decisions stochastically, starting with my current coin-based intermittent fasting and dice-based kettlebell.

So I have been doing stochastic intermittent fasting for a while, and recently started doing stochastic cardio.

Coinfasting: flip a coin in the morning. Heads eat, tails fast. Over 7 days the expected value is 3.5, identical to a scheduled ADF. The randomness makes it easier to calibrate on the right number of calories: you can't just binge because the next few days may also be heads, and you can't do too much restriction because the next few days may also be tails.

Coin cardio: 20 minutes cycling every morning. Heads days, an extra 30 minutes cycling in the afternoon. 140 minutes baseline, which is the minimum suggested dose, averages to 245 minutes, maximum 350 minutes. 450 minutes is the maximum suggested dose of cardio beyond which diminishing returns kick in (https://well.blogs.nytimes.com/2015/04/15/the-right-dose-of-exercise-for-a-longer-life/).

Dice Kettlebell: What I had been doing was: roll 2d6, multiply by a number. Do that many swings. I decided to simplify this a bit by just increasing the multiplier and rolling one die.

Basically: I am enjoying the hell out of adding all this randomness to my life. I want to add more, hence this project.

I want to automate this stuff and make it easy to extend flipism to other parts of my life.

What I've been doing is recording the day's results of the coinflip and dice roll in a pinned Keep note. Note to self: check if Keep has an API that I can use to send stuff to from racket.

I had originally envisioned simple decision scripts, some depending on the decisions of the last week. Drink some water? How many kettlebell swings should I do today? etc. For some reason I am now making an RPG. There's a statsheet. I'm gonna go with the flow and see where it ends up.

Check out index.md to see what I'm already working on.

Note: I do not believe in adding UI. I prefer building my own UI on the fly, and view even the existence of UI as too opinionated for my tastes. Do not expect user friendliness.

This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License

lifescripts's Issues

Cleaning.rkt doesn't use the laziness stat

It currently doesn't know how lazy I am, or care. It should skillcheck laziness and offer up the simpler tasks the more lazy I am.

No CLI arguments yet

Add basic argv functionality.

Cleaning.rkt doesn't limit tasks of various complexities

Since the user manually edits the tasks lists, there's not even an attempt to constrain these lists to, say, 6 tasks.

Skills versus stats

Scripts such as gripper, hydrate, etc perform a skillcheck based on tertiary stats such as Laziness and Thirst.

How should skills be implemented?

Need: logging

Use a logger to write history to output.

Inconsistent methods

cussout.rkt works differently than engagetroll, sometimes the result is negated for success and other times it's taken straight. It's rather muddled.

Make it all work consistently, following a single standard.

Status is indirect

Implement today > status directly

Cleaning.rkt requires manually editing tasks into it

Make a tasks.rkt file that it reads from and selects based on a cli argument

Tasklists should be simple line-separated lists, not code.

User should be able to simply echo "foo bar" >> instant-tasks to add it, etc.

Add task recipes

The ability to string together several task lists and reuse them; "prepare for holiday" "prepare for guests" etc.

Saving throws are incorrect

They're muddied. Redo from scratch.

Cleaning.rkt doesn't track anything

Right now, it just spits out a random task that the user has to manually edit into a list. It doesn't even attempt to track whether it is done, cross it off, etc.

Is this intentional, or due to laziness and incompetence? Yes.

Nonstandardized script output

Some scripts output directly, others do not.

Standardize on no direct output.