@@ 1,6 1,8 @@
Alisa's paths forward policy
=================
+Last updated 2019-11-03.
+
[TOC]
# Introduction
@@ 10,7 12,7 @@ This document describes some things I pl
- help prevent myself from getting stuck in any area of my life and
- hold myself accountable for engaging with criticism from any external source.
-This document is inspired by [Elliot Temple's Paths Forward Policy](https://curi.us/2068-my-paths-forward-policy).
+This document was inspired by [Elliot Temple's Paths Forward Policy](https://curi.us/2068-my-paths-forward-policy).
You can view the [latest version of this document on sourcehut](https://hg.sr.ht/~petrogradphilosopher/fi/raw/default/pf.md). You can also view the [history of changes](https://hg.sr.ht/~petrogradphilosopher/fi/log).
@@ 22,13 24,13 @@ Note: By "FI post" I mean a [Fallible Id
If someone believes I'm making a mistake and wants to explain my mistake to me, I want there to be a reasonable way for them to do so.
-## Post to FI often enough
+## Post to FI every day
-I plan to make FI posts often enough to get enough feedback to keep making progress. My goal is to post at least once per day.
+My goal is to post at least once per day, except when I'm taking a break. I may take up to two breaks per year, each of which could last for up to two weeks.
## Keep my FI posting error rate low
-[In order to learn, one's error rate needs to be sufficiently low](http://fallibleideas.com/gradualism). I plan to keep my FI posting error rate low enough that I can [write a postmortem for every posting mistake I find out about](http://curi.us/2190-errors-merit-post-mortems).
+[In order to learn, one's error rate needs to be sufficiently low](http://fallibleideas.com/gradualism). I plan to keep my FI posting error rate low enough that I can [write a postmortem for every posting mistake I find out about](http://curi.us/2204-alisa-discussion#12940).
## Update this document often enough
@@ 36,7 38,7 @@ I plan to update this document at least
# Escalation policy
-I plan to grant at least 15 minutes per month of time spent reconsidering this document, per person, to people who want to suggest a change to this document. Exception: I will allocate at least 4 hours per month, combined, to the top FI list posters, namely:
+I plan to grant at least 15 minutes per month of time spent reconsidering this document, per person, to people who want to suggest a change to this document. Exception: I will allocate at least 4 hours per month, combined, to the top FI list posters, whom I regard as:
- Elliot Temple
- Jordan Talcot
@@ 52,17 54,11 @@ Here is a list of things I am learning t
## Typos and grammar errors
-I plan to listen to each sentence with text-to-speech (TTS) before sending. Any edits to a clause trigger a new listen to that clause.
-
-TTS is effective for catching typos that are audible when read out loud. It doesn't catch mistakes such as using the wrong homonym.
-
-I started using TTS for many of my FI posts in 2018-05. I started using TTS for all of my FI posts [in 2019-08](http://curi.us/2204-alisa-discussion#c13201).
+I plan to listen to each sentence with text-to-speech (TTS) before sending. Any edits to a clause trigger a new listen to that clause. I posts in 2018-05. I started using TTS for all of my FI posts [in 2019-08](http://curi.us/2204-alisa-discussion#c13201).
-In 2018-05, I tried reading each sentence out loud instead of using TTS. However, it was difficult to notice certain kinds of mistakes this way. For example, it wasn't effective for catching doubled words.
-(I worked around this by [configuring my editor to highlight doubled words](https://groups.google.com/d/msg/fallible-ideas/b937ywe6LYI/4r9rsGLiCgAJ).)
-It also wasn't effective for catching case in which [I mis-numbered an element of a numbered list](https://groups.google.com/d/msg/fallible-ideas/b937ywe6LYI/Z9k1JacoCwAJ).
+I plan to check every post for words that occur exactly once in my post *and* that occur neither in the system dictionary nor in my personal dictionary.
-It's easier for me to notice mistakes by looking away from the screen and listening to TTS than by looking at the screen and reading it myself. I want quick, reliable feedback on a wide variety of typos. TTS gives me that.
+It's easier for me to notice mistakes by looking away from the screen and listening to TTS than by looking at the screen and reading it myself. I want quick, reliable feedback on a wide variety of typos. TTS provides that.
## Topic sentences
@@ 75,7 71,7 @@ The idea of scanning for topic sentences
## Clarity of references
-References are words/phrases like "it", "he", "they", "the argument", etc. To help with clarity, I plan to check whether or not each reference is better than replacing it with a statement of the thing being referenced. This check was suggested by [Elliot Temple in an FI list post on 2018-04-24](https://groups.google.com/d/msg/fallible-ideas/vqRGArolXEs/b2eFQAD_AQAJ). Any error in clarity of referencdes counts as an error.
+References are words/phrases like "it", "he", "they", "the argument", etc. To help with clarity, I plan to check whether or not each reference is better than replacing it with a statement of the thing being referenced. This check was suggested by [Elliot Temple in an FI list post on 2018-04-24](https://groups.google.com/d/msg/fallible-ideas/vqRGArolXEs/b2eFQAD_AQAJ). Any error in clarity of references counts as an error.
## Explaining thinking