On Sun, Mar 25, 2018 at 12:35:36PM -0700, Elliot Temple wrote:
> On Mar 25, 2018, at 12:16 PM, Jordan Talcot wrote:
>> sometimes i recognize that i am just putting off writing the email. i don’t *really* need to do the other thing right now. i could write the email first and *then* do the other thing.
>
> have you tried alternating emails and other stuff? write an email, do a different thing, write another email, do another different thing. you can do short emails and short chunks of other things and keep getting both done!
Makes sense. I shouldn't feel like I have to work on a single thing for a long time just because I started it. I will learn something even in a short time. I can't predict the growth of knowledge. What I learn will affect what I choose to do next.
> also if you have trouble with emails, it’s good to try lots of times, even if the attempts are only 2 minutes long and you stop after that if you’re stuck. you can try for 2 minutes and give up on emailing and do something else. but then you try again for 2 minutes after that, 5-10 minutes later. you could fail several times per hour. that’d be good. you won’t always fail. and if you do manage to fail 10 times in a row, you’d get good data. you’d have more chance to see patterns in how and why you fail at emailing.
Really interesting point here about how even many failures in a row would yield knowledge. No matter whether you succeed at the object level task or not, there's knowledge to be gained. I can't predict the growth of knowledge, so I shouldn't skip the trying part just because I think I know what the outcome will be.
> some people try and fail for hours, or not at all. if it’s such a big deal, it’s hard to start. starting should be cheap. stopping should be cheap.
Interesting point. Starting and stopping should be cheap. Easy. Lightweight. Like thinking of ideas. You're not committing to do something for a certain amount of time just because you start doing it.
>> with this particular reply, i hit reply to make a draft, then just stared at it for a few seconds. then immediately thought “oh, i should go get another coffee”. which was actually kind of weird because i’ve only been drinking one coffee each morning, not two. (btw, i think i shouldn’t drink coffee in this way at all - i shouldn’t be drinking coffee every single day like that.)
>>
>> i didn’t go get the coffee. i decided to start writing instead. i figured i would try to write a reply and see how it goes. then if it felt too hard, i could re-evaluate. but i should at least *try* before i give up or go do something else.
>>
>> that is a problem i frequently have with emails. i look at something and it seems like it *might* be hard, so i don’t even start. i just avoid doing it at all.
>
> and once you start/try, it’s sometimes easy within 1 minute, right?
>
> Yes.
>
> > not every time, but reasonably often. so if you just start/try a lot, lots of times it’ll work, and other times you could just stop after it doesn’t work for 2 minutes. and then you’ll write lots of emails and never spend an hour having a rough time (unless you really want to).
Yes. I can't predict the growth of knowledge. I should try the activity, see what happens, and if I run into a problem, acknowledge the problem, and try to solve it. Trying to solve it could involve switching to something else, finding a way to break it into pieces, finding an easier part of it to do at first, asking someone for help, or other things.
I was thinking that by starting an activity I was committing to finishing it or working on it for some amount of time, regardless of what I learned after starting it. No wonder I dread starting things.
> you could write down things you find hard or get stuck on. keep a count of broad categories. like “got stuck on the subject line” or “felt bad” or “wanted to do a distraction like get coffee or wash dishes” or “didn’t know what to say”.
Good point. I could guess some ideas about what I'm getting stuck on, and take notes. This is just general learning stuff, but applied in an area where I hadn't thought to apply it: to doing tasks that I avoid or get stuck on.
>> there is a difference between this and how i was approaching it before. before i would start the email with the goal of *finishing* the email. so anything less than finished & sending an email felt like a failure. and i felt pressured & stuck if i had trouble and didn’t know what to write.
>
> the goal with activities should be to *try* them. you get started and see how it goes. either it goes well or you run into a problem. if you run into a problem, you can try to solve it or learn more about it or whatever. (but don’t ignore the problem and keep going. note that judging the problem doesn’t really matter, and then continuing, wouldn’t be ignoring it. that would be making a judgement about how to deal with it. don’t just ignore it and hoping things turn out ok. make a judgement about what to do. the judgement can be fast.)
>
> this stuff isn’t just for writing emails. it’s also how to read books or do any activity. any time i recommend stuff, it’s meant to be done this way: try it, get started, see how it goes. if it’s going great, cool, do more. if there’s a problem, ok, that’s a new situation to be dealt with. finding a problem is progress. if you try the thing i recommended and find a problem, that’s good, progress was made. you don’t have to do the whole thing all at once.
This is recommending a piecemeal, incremental approach to doing things in general. It makes sense. Do a little bit, see how it goes, adjust. It's kind of like [Avoiding Coercion](
http://fallibleideas.com/avoiding-coercion) but for activities, in the sense that you don't keep doing something that doesn't work when you're not making progress.
> another good thing about how to approach activities is to view everything as *practice*. instead of writing emails, you’re *practicing* writing emails. (and in line with my ideas about powering up and only doing what’s easy, the basic goal is to keep practicing until your practice emails are good. instead of stopping practicing to try to accomplish some goal, just keep learning to the point your practice itself can cheaply and easily accomplish your goals.)
Makes sense. Rather than viewing the task itself as the main benefit, I view my learning as the main benefit. Accomplishing the task itself is only a nice side effect. This "learning-first" approach requires me to choose tasks that I can work on with a manageable error rate.
This piecemeal approach would also work on items in my FI queue. I can just do a little bit on the first item in any of the queues and see how it goes.