# My Hammertime Final Exam

Firstly, I finally made it :~D

It's my second attempt, firstly I tried to finish [Hammertime](https://www.lesswrong.com/s/qRxTKm7DAftSuTGvj) around a year ago. I even forgot I had a LessWrong profile since, so here I am, writing my first post.

### Prompts

1.  Design a instrumental rationality technique.
2.  Introduce a rationality principle or framework.
3.  Describe a cognitive defect, bias, or blindspot.

Rationality Principle: One change at the time
---------------------------------------------

I kinda got used to be a professional at my career, but as soon as I start to deal with routine real-life problems, my thoroughly collected knowledge suddenly disappears :~0

For example, every time I begin a task, I have to remind myself that I **should** do as small changes as possible: that way (in case anything goes wrong) only as small part of system will be broken; plus it's easier to review and test small changes. So every task I have to fight my urge to add "another little change" or "do a tiny refactoring".

So that's where some life situation begins -- like replacing a trash bag, -- and I suddenly find myself out in the bathroom cleaning the mirror, with small 2-minute task scope grown into 2-hour monster. That's why amygdala starts to learn a pattern "to change a trash bag is a costly operation".

While I studied productivity, I've heard that people who begin buidling planning/productivity system stuff tend to "**overpush**" extra tasks: systematization brings as feeling that every task is *finishable*, and even better -- in a shorter time. So what? -- I'll take two :~D

But that's a catch. You begin to grow in planning when you start to deny "maybe" tasks to keep the space for "definitely yes!" tasks. At least, that's what they've been telling me for 2 years :~D

Rationality technique: Reversible
---------------------------------

One of my job's parts is to write release plans. Sometimes they're as simple as:

**Deploy**:

1.  deploy the backend (no breaking changes, no migrations)

**Rollback**:

1.  rollback the backend via Pipelines UI

Sometimes there's a database schema change where's my colleague needed:

**Deploy**:

1.  deploy the backend (no breaking changes)
2.  migrations applied automatically (head\_revision=123abc, down\_revision=**bca521**)

**Rollback**:

1.  rollback the migration: `alembic downgrade bca521`
2.  rollback the backend via Pipelines UI

Sometimes there are other team members so plan becomes bigger:

**Deploy**:

1.  deploy the backend (no breaking changes)
2.  migrations applied automatically (head\_revision=123abc, down\_revision=**bca521**)
3.  deploy the fronted

**Rollback**:

1.  rollback the frontend via Pipelines UI
2.  rollback the migration: `alembic downgrade bca521`
3.  rollback the backend via Pipelines UI

And so on... So what's that about? -- we tend to not think about "planned fall", usually we only think about potential problems like:

*   if I move to another country I might not like it
*   if I find a new job then my boss might be mean
*   if I have an operation under general anesthesia then I might wake up conscious at the middle of it -- and have PTSD for the rest of my life

Not all of this problems have a way to return everything to the starting point, though usually there's a way to compensate. And it's likely that you not only need to plan a "rollback" part, but also to modify a "rollout" part to make it *more reversible*. So instead of:

**Rollout**:

1.  find a doctor
2.  prepare of operation
3.  have an operation

**Rollback**:

1.  cry

one could possible have:

**Rollout**:

1.  find a doctor
2.  (look for bad consequences statistics)
3.  ask gf to care for me a night after operation
4.  prepare of operation
5.  bring something yummy
6.  have a favorite show episodes downloaded to my phone's storage
7.  have an operation

**Rollback:**

1.  eat yummies and binge-watch the whole season during the night
2.  call a psychotherapist

Cognitive defect: eternity
--------------------------

We don't see things the way they are. But what's more important, we don't see **how things change** the way they do.

Couple years ago I thought that I'd never get off the energy drinks as I couldn't go without them even for a week. Gradually my patience led to one breakdown a month, then to 1 breakdown/couple months. I started to unwind the vicious cycle and it occurs to be easier to refuse doing bad habits.

So what if current "giant problems" are already being solved with small steps? At the moment it might seem to take the eternity to do something, but as long as you keep your pace, things change :~D