https://www.whitehouse.gov/blog/2016/05/03/preparing-future-artificial-intelligence

This is the public group rationality diary for February, 2016. It's a place to record and chat about it if you have done, or are actively doing, things like:

• Established a useful new habit

• Obtained new evidence that made you change your mind about some belief

• Decided to behave in a different way in some set of situations

• Optimized some part of a common routine or cached behavior

• Consciously changed your emotions or affect with respect to something

• Consciously pursued new valuable information about something that could make a big difference in your life

• Learned something new about your beliefs, behavior, or life that surprised you

• Tried doing any of the above and failed

Or anything else interesting which you want to share, so that other people can think about it, and perhaps be inspired to take action themselves. Try to include enough details so that everyone can use each other's experiences to learn about what tends to work out, and what doesn't tend to work out.

Nate Soares recommends pairing up when studying, so I figured it would be useful to facilitate that.

If you are looking for a study partner, please post a top-level comment saying:

• What you want to study
• Your level of relevant background knowledge
• If you have sources in mind (MOOCs, textbooks, etc), what those are
• Your time zone

https://www.reddit.com/r/science/comments/3nyn5i/science_ama_series_stephen_hawking_ama_answers/

the vast majority of the discussion is about AI risk.

Previous thread: http://lesswrong.com/lw/mnq/instrumental_rationality_questions_thread/

This thread is for asking the rationalist community for practical advice.  It's inspired by the stupid questions series, but with an explicit focus on instrumental rationality.

Questions ranging from easy ("this is probably trivial for half the people on this site") to hard ("maybe someone here has a good answer, but probably not") are welcome.  However, please stick to problems that you actually face or anticipate facing soon, not hypotheticals.

As with the stupid questions thread, don't be shy, everyone has holes in their knowledge, though the fewer and the smaller we can make them, the better, and please be respectful of other people's admitting ignorance and don't mock them for it, as they're doing a noble thing.

(See also the Boring Advice Repository)

These ideas came out of a recent discussion on actually trying at Citadel, Boston's Less Wrong house.

What does "Actually Trying" mean?

Actually Trying means applying the combination of effort and optimization power needed to accomplish a difficult but feasible goal. The effort and optimization power are both necessary.

Failure Modes that can Resemble Actually Trying

Pretending to try

Pretending to try means doing things that superficially resemble actually trying but are missing a key piece. You could, for example, make a plan related to your goal and diligently carry it out but never stop to notice that the plan was optimized for convenience or sounding good or gaming a measurement rather than achieving the goal. Alternatively, you could have a truly great plan and put effort into carrying it out until it gets difficult.

Trying to Try

Trying to try is when you throw a lot of time and perhaps mental anguish at a task but not actually do the task. Writer's block is the classic example of this.

Sphexing

Sphexing is the act of carrying out a plan or behavior repeatedly despite it not working.

The Two Modes Model of Actually Trying

Actually Trying requires a combination of optimization power and effort, but each of those is done with a very different way of thinking, so it's helpful to do the two separately. In the first way of thinking, Optimizing Mode, you think hard about the problem you are trying to solve, develop a plan, look carefully at whether it's actually well-suited to solving the problem (as opposed to pretending to try) and perhaps Murphy-jitsu it. In Executing Mode, you carry out the plan.

Executing Mode breaks down when you reach an obstacle that you either don't know how to overcome or where the solution is something you don't want to do. In my personal experience, this is where things tend to get derailed. There are a few ways to respond to this situation:

• Return to Optimizing Mode to figure out how to overcome the obstacle / improve your plan (good),
• Ask for help / consult a relevant expert (good),
• Take a break, which could lead to a eureka moment, lead to Optimizing Mode or lead to derailing (ok),
• Sphex (bad),
• Derail / procrastinate (bad), or
• Punt / give up (ok if the obstacle is insurmountable).

The key is to respond constructively to obstacles. This usually means getting back to Optimizing Mode, either directly or after a break.  The failure modes here are derailing immediately, a "break" that turns into a derailment, and sphexing.  In our discussion, we shared a few techniques we had used to get back to Optimizing Mode.  These techniques tended to focus on some combination of removing the temptation to derail, providing a reminder to optimize, and changing mental state.

Getting Back to Optimizing Mode

Context switches are often helpful here.  Because for many people, work and procrastination both tend to be computer-based activities, it is both easy and tempting to switch to a time-wasting activity immediately upon hitting an obstacle.  Stepping away from the computer takes away the immediate distraction and depending on what you do away from the computer, helps you either think about the problem or change your mental state.  Depending on what sort of mood I'm in, I sometimes step away from the computer with a pen and paper to write down my thoughts (thinking about the problem), or I may step away to replenish my supply of water and/or caffeine (changing my mental state).  Other people in the discussion said they found going for a walk or getting more strenuous exercise to be helpful when they needed a break.  Strenuous exercise has the additional advantage of having very low risk of turning into a longer-than-intended break.

The danger with breaks is that they can turn into derailment.  Open-ended breaks ("I'll just browse Reddit for five minutes") have a tendency to expand, so it's best to avoid them in favor of things with more definite endings.  The other common say for breaks to turn into derailment is to return from a break and go to something non-productive.  I have had some success with attaching a sticky-note to my monitor reminding me what to do when I return to my computer.  I have also found that if the note makes clear what problem I need to solve also makes me less likely to sphex when I return to my computer.

In the week or so since the discussion that inspired this post, I have found that asking myself "what would Actually Trying look like right now?" This has helped me stay on track when I have encountered difficult problems at work.

Discussion article for the meetup : Cambridge Less Wrong Meetup - Book Recommendations

Discussion article for the meetup : Cambridge Less Wrong Meetup - Book Recommendations

Discussion article for the meetup : Boston Meetup

Discussion article for the meetup : Boston Meetup

This thread is for asking the rationalist community for practical advice.  It's inspired by the stupid questions series, but with an explicit focus on instrumental rationality.

Questions ranging from easy ("this is probably trivial for half the people on this site") to hard ("maybe someone here has a good answer, but probably not") are welcome.  However, please stick to problems that you actually face or anticipate facing soon, not hypotheticals.

As with the stupid questions thread, don't be shy, everyone has holes in their knowledge, though the fewer and the smaller we can make them, the better, and please be respectful of other people's admitting ignorance and don't mock them for it, as they're doing a noble thing.

(See also the Boring Advice Repository)

Discussion article for the meetup : Boston: Unconference

Discussion article for the meetup : Boston: Unconference