Less Wrong is a community blog devoted to refining the art of human rationality. Please visit our About page for more information.

In support of yak shaving part 2

1 Elo 26 April 2017 01:41AM

part 1 of yak shaving.  It wan necessary to write part two because part 1 was not clear enough about what the problem is.  I don't disagree with the comments, and I apologise for not presenting it better in the first round. (part 1 on lesswrong)

Original post: http://bearlamp.com.au/yak-shaving-2/


You decide today is a day for getting things done, it is after all your day off.  You do what any person concerned with work does.  You sit down at your desk.  When you do you notice two empty tea cups and a one-sip-left in a can of soft drink.  Not liking a messy environment you figure you will quickly tidy up.  You take the teacups and put them on the kitchen bench.  You take the can to the recycling bin when you realise it's full and needs to be taken out to the garbage bin.

You take the rubbish to the garage and realise tonight is bin night anyway so you put the recycling bin.  While you are at it you put all the bins to the curb.  You get back to the kitchen and find the teacup is actually sitting on a pile of unopened mail.  You open what looks like the bills in the pile and mentally note to deal with them when you get back to your desk.  so you leave them on the kitchen table to take back with you.

You get to the teacups and realise you are out of dishwashing detergent.  You will have to go buy some.  You go to get the car keys and notice the washing basket is full.  You decide to quickly put the washing on before you go.  That will save time.  You get in the car and discover it's nearly out of petrol.  And the supermarket is it the other direction from the petrol station.

While you are out you grab a coffee and lunch before getting back.  Then you hit traffic and get home quite late.  You bring in the mail but notice the mailbox post is rotting.  you have some spare wood in the garage but your work bench has the remnants of when you tried to fix the shelf for your bathroom.  You could just fix the mailbox post with cable ties but how long would that last?

With a stubborn determination to get SOMETHING done today you take the mailbox into your work bench, and start working on top of the other project because you basically have no choice any more.  When you go to measure and mark the wood it seems like every pencil needs sharpening, as does the saw.  The drill has a flat battery, the last drill bit of the right size is broken, you have only three screws that are galvanised and one that is not.  you drill the guide hole too small, bend a screw in the process of getting it into the wood, slip and wound the bathroom shelf project, and eventually re-assemble a mailbox.  

You get the mailbox on the fence but it's getting dark and you need dinner.  You can't help but wonder where the day went.  It feels like you worked hard all day but you barely have anything to show for it.

Tomorrow you are back at work but maybe you need to take another day off, a tantalising prospect...  You have a deal with your boss that you can take the day off only if you could explain why you need another day off.  Of course that might require writing a note, which might require a working pen from the stationary cupboard, or sending an email, which you swore to not do before reading all the unread ones that are waiting for you...  And it would be nice to pay those bills.


In part 1 I said:

The problem here is that you spent all day shaving yaks (see also “there’s a hole in my bucket“).  In a startup that translates to not doing the tasks that get customers – the tasks which get money and actually make an impact, say “playing with the UI”.  It’s easy to see why such anti-yak shaving sentiment would exist (see also: bikeshedding, rearranging deck chairs on the titanic, hamming questions).  You can spend a whole day doing a whole lot of nothings; getting to bed and wonder what you actually accomplished that day (hint: a whole lot of running in circles).

It’s not just one problem, but a series of problems that come to your attention in a sequence.

this sort of behaviour is not like bikeshedding at all.  Nor is it doing insignificant things under the guise of “real work”.  Instead this is about tackling what stands in the way of your problem.  In problem solving in the real world, Don’t yak shave” is not what I have found to be the solution.

I propose that yak shaving presents a very important sign that things are broken.

The scenario above is my version of hell incarnate.  Real life is probably not that bad but things like that come up all the time.  They act as open loops, tax your mind (kind of like the debatable ego depletion concept) and don't really represent you being in a good place.

If something is broken, and you are living with it, that’s not acceptable.  You need a system in your life to regularly get around to fixing it.  Notepadsreviews, list keeping, set time aside for doing it and plan to fix things.

So I say, Yak Shave, as much, as long, and as many times as it takes till there are no more yaks to shave.


Accruing or resolving problems?

A question worth asking is whether you are in your life at present causing a build up of problems, a decrease of problems, or roughly keeping them about the same level.

If you are a person who keeps quantified tracking of yourself - this might be easier to answer. than if you do less tracking.  maybe you have to do lists, maybe some notepads, any way to know if you are getting better or worse at this.

The answer is probably something like, "up and down".  You do both, over time.  Things build up and then things resolve.  If you see things as having always built up, or gradually gotten worse...  Maybe it's time to stop.  Think.  Ask yourself...

What's going on?


Meta: this took 1.5hrs to write.  

Part 1: In support of yak shaving.  I would recommend a quick read over it.  I don't honestly want to quote the entire thing here but it's so so so so so relevant.

Original post:  http://bearlamp.com.au/yak-shaving-2/

Up next: Working with multiple problems at once

An inquiry into memory of humans

2 Elo 19 April 2017 07:02AM

Cross posted from: http://bearlamp.com.au/an-inquiry-into-memory-of-humans/

In trying to understand how my memory for people works, I am trying to investigate in what order my people semantic network is arranged.

For each exercise that follows you will need to think of a different person to avoid priming yourself with the people you have already thought of.


Think of a person you know.  What comes to mind to represent them?  Is it their name?  Is it their face?  Is it some other sensory or other detail?

Think of a face of a person you know.  What else comes to mind?  Can you think of a person’s face without other details like names coming up.  How about without their hair.  Try this for 3 or more people you know.

Think of a person who has a characteristic voice.  Can you represent the idea of this person without linking to other details of this person?  without their face?  Without their name?  What about a radio presenter who’s face you have never seen?  Can you represent their voice without their face? Without their name?

Think of a person who you can recognise by a characteristic touch.  Think of someone’s handshake that you remember.  Can you represent the concept of the person via handshake alone?  Can you hold off from recalling their name?

Think of a person you can recall that has worn black clothing.  Someone who has worn white clothing.  Are they an idea alone?  Or is it hard to describe without their name?

Think of someone who you can remember singing.  Can you remember their singing selves without the face?  Without the name?

Think of a person’s name.  Do you know who this person is without their face?  Do you know what they sound like without knowing what they look like?  How do you navigate from one detail to another?

Think of a person who is particularly spiritual.  Can you represent who they are without bringing their name to mind?

I could go on but I leave the rest as an exercise to the reader to make up and experiment with a few more examples.  In smells, and in any other sensory experiences, in methods of dividing people.  Tall, short, grumpy…


So What?

Memory is this weird thing.  If you want to know how to take the most advantage of it, you need to know how it works.  This exercise hopefully makes you ask and wonder about how it works.

What do you remember easily.  What details come straight to mind, what details are hard.  Each person would be different in subtle ways, and with knowledge of that difference you can better ask the questions:

Am I going to naturally remember this?

How am I going to format this information in such a way that I can remember it?

In the book Peak, Anders suggests that to tap into the power of deliberate practice you need to add new knowledge to the foundation of old knowledge.

I can’t honestly tell you how to use your memory but I hope this exercise is a step in the right direction.


Meta: I spend a few days this week introspecting and wondering.  I apologise for not being able to deliver an insight.  Only questions.

This took 50mins to write and is the first piece I typed in Colemak not Qwerty after relearning how to type (story coming soon).

Open thread, Apr. 03 - Apr. 09, 2017

1 Elo 03 April 2017 06:58AM

Notes for future OT posters:

1. Please add the 'open_thread' tag.

2. Check if there is an active Open Thread before posting a new one. (Immediately before; refresh the list-of-threads page before posting.)

3. Open Threads should start on Monday, and end on Sunday.

4. Unflag the two options "Notify me of new top level comments on this article" and "

Deriving techniques on the fly

3 Elo 31 March 2017 10:03AM

Original post:  http://bearlamp.com.au/deriving-techniques-on-the-fly/


Last year Lachlan Cannon came back from a CFAR reunion and commented that instead of just having the CFAR skills we need the derivative skills.  The skills that say, "I need a technique for this problem" and let you derive a technique, system, strategy, plan, idea for solving the problem on the spot.

By analogy to an old classic,

Give a man a fish and he will eat for a day.  Teach a man to fish and he never go hungry again.

This concept always felt off to me until I met Anna.  An american who used to live in Alaska where they have enough fish in a river that any time you go fishing you catch a fish, and a big enough one to eat.  In contrast, I had been fishing several times when I was little (in Australia) and never caught things, or only caught fish that were too small to feed one person, let alone many people.

Silly fishing misunderstandings aside I think the old classic speaks to something interesting but misses a point.  to that effect I want to add something.

Teach a man to derive the skill of fishing when he needs it. and he will never stop growing.

We need to go more meta than that?  I am afraid it's turtles all the way down.


Noticing

To help you derive you need to start by noticing when there is a need.  There are two parts to noticing:

  1. triggers
  2. introspection
  3. What next

But before I fail to do it justice, agentyduck has written about this. Art of noticingWhat it's like to notice thingsHow to train noticing.  

The Art Of Noticing goes like this:

  1. Answer the question, "What's my first possible clue that I'm about to encounter the problem?" If your problem is "I don't respond productively to being confused," then the first sign a crucial moment is coming might be "a fleeting twinge of surprise". Whatever that feels like in real time from the inside of your mind, that's your trigger.

  2. Whenever you notice your trigger, make a precise physical gesture. Snap your fingers, tap your foot, touch your pinky finger with your thumb - whatever feels comfortable. Do it every time you notice that fleeting twinge of surprise.


How To Train Noticing

  1. I guess. I remember or imagine a few specific instances of encountering weak contrary evidence (such as when I thought my friend wasn't attracted to me, but when I made eye contact with him across the room at a party he smiled widely). On the basis of those simulations, I make a prediction about what it will feel like, in terms of immediate subjective experience, to encounter weak contrary evidence in the future. The prediction is a tentative trigger. For me, this would be "I feel a sort of matching up with one of my beliefs, there's a bit of dissonance, a tiny bit of fear, and maybe a small impulse to direct my attention away from these sensations and away from thoughts about the observation causing all of this".
  2. I test my guess. I keep a search going on in the background for anything in the neighborhood of the experience I predicted. Odds are good I'll miss several instances of weak contrary evidence, but as soon as I realize I've encountered one, I go into reflective attention so I'm aware of as many details of my immediate subjective experience as possible. I pay attention to what's going on in my mind right now, and also what's still looping in my very short-term memory of a few moments before I noticed. Then I compare those results to my prediction, noting anything I got wrong, and I feed that information into a new prediction for next time. (I might have gotten something wrong that caused the trigger to go off at the wrong time, which probably means I need to narrow my prediction.) The new prediction is the new trigger.
  3. I repeat the test until my trigger seems to be accurate and precise. Now I've got a good trigger to match a good action.

Derivations (as above) are a "what next" action.  

My derivations come from asking myself that question or other similar questions, then attempting to answer them:

  • What should I do next?
  • How do I solve this problem?
  • Why don't other people have this problem?
  • Can I make this problem go away?
  • How do I design a system to make this not matter any more?

(you may notice this is stimulating introspection - this is what it is)


Meta:

The post that led me to post on derivations is this post on How to present a problem hopefully to be published tomorrow.

This post took ~1 hour to write.

Cross posted to lesswrong

Meetup : April Pub meetup + SlateStarCodex meetup

0 Elo 30 March 2017 07:44AM

Discussion article for the meetup : April Pub meetup + SlateStarCodex meetup

WHEN: 20 April 2017 07:00:00PM (+1100)

WHERE: lvl2, 565 George st, Sydney

You can find us sitting at the large table outside the pizza oven. Come along to our regular monthly pub meetup to talk all things math, science, technology, engineering, thinking, growth, reasoning and beliefs. If you are an aspiring rationalist, a nerd, geek, scientist or just a quiet thinker - we can't wait to meet you to share ideas, discuss, debate, learn and grow together. This month also includes the Global SlateStarCodex meetup,

http://slatestarcodex.com/2017/03/27/ssc-meetup-everywhere/

See you there! Also, while you are at it - bring a friend along too!

https://www.facebook.com/events/180273879151236/

call 0438481143 if you are lost

https://www.meetup.com/lesswrong-Sydney0/events/238822756/

Discussion article for the meetup : April Pub meetup + SlateStarCodex meetup

[Link] My Notes on the book, "Turn the ship around" by L David Marquet

3 Elo 30 March 2017 06:32AM

Announcing: The great bridge

9 Elo 17 March 2017 01:11AM

Original post: http://bearlamp.com.au/announcing-the-great-bridge-between-communities/


In the deep dark lurks of the internet, several proactive lesswrong and diaspora leaders have been meeting each day.  If we could have cloaks and silly hats; we would.

We have been discussing the great diversification, and noticed some major hubs starting to pop up.  The ones that have been working together include:

  • Lesswrong slack
  • SlateStarCodex Discord
  • Reddit/Rational Discord
  • Lesswrong Discord
  • Exegesis (unofficial rationalist tumblr)

The ones that we hope to bring together in the future include (on the willingness of those servers):

  • Lesswrong IRC (led by Gwern)
  • Slate Star Codex IRC
  • AGI slack
  • Transhumanism Discord
  • Artificial Intelligence Discord

How will this work?

About a year ago, the lesswrong slack tried to bridge across to the lesswrong IRC.  That was bad.  From that experience we learnt a lot that can go wrong, and have worked out how to avoid those mistakes.  So here is the general setup.

Each server currently has it's own set of channels, each with their own style of talking and addressing problems, and sharing details and engaging with each other.  We definitely don't want to do anything that will harm those existing cultures.  In light of this, taking the main channel from one server and mashing it into the main channel of another server is going to reincarnate into HELL ON EARTH.  and generally leave both sides with the sentiment that "<the other side> is wrecking up <our> beautiful paradise".  Some servers may have a low volume buzz at all times, other servers may become active for bursts, it's not good to try to marry those things.

Logistics:

Room: Lesswrong-Slack-Open

Bridged to:

  • exegesis#lwslack_bridge
  • Discord-Lesswrong#lw_slack_main
  • R/rational#lw_slack_open
  • SSC#bridge_slack

I am in <exegesis, D/LW, R/R, SSC> what does this mean?

If you want to peek into the lesswrong slack and see what happens in their #open channel.  You can join or unmute your respective channel and listen in, or contribute (two way relay) to their chat.  Obviously if everyone does this at once we end up spamming the other chat and probably after a week we cut the bridge off because it didn't work.  So while it's favourable to increase the community; be mindful of what goes on across the divide and try not to anger our friends.

I am in Lesswrong-Slack, what does this mean?

We have new friends!  Posts in #open will be relayed to all 4 children rooms where others can contribute if they choose.  Mostly they have their own servers to chat on, and if they are not on an info-diet already, then maybe they should be.  We don't anticipate invasion or noise.

Why do they get to see our server and we don't get to see them?

So glad you asked - we do.  There is an identical set up for their server into our bridge channels.  in fact the whole diagram looks something like this:

Server Main channel Slack-Lesswrong Discord-Exegesis Discord-Lesswrong Discord-r/rational Discord-SSC
Slack-Lesswrong Open   lwslack_bridge lw_slack_main lw_slack_open bridge_slack
Discord-Exegesis Main #bridge_rat_tumblr   exegesis_main exegesis_rattumb_main bridge_exegesis
Discord-Lesswrong Main #Bridge_discord_lw lwdiscord_bridge   lw_discord_main bridge_lw_disc
Discord-r/rational General #bridge_r-rational_dis rrdiscord_bridge reddirati_main   bridge_r_rational
Discord-SSC General #bridge_ssc_discord sscdiscord_bridge ssc_main ssc_discord_gen  

Pretty right? No it's not.  But that's in the backend.

For extra clarification, the rows are the channels that are linked.  Which is to say that Discord-SSC, is linked to a child channel in each of the other servers.  The last thing we want to do is impact this existing channels in a negative way.

But what if we don't want to share our open and we just want to see the other side's open?  (/our talk is private, what about confidential and security?)

Oh you mean like the prisoners dilemma?  Where you can defect (not share) and still be rewarded (get to see other servers).  Yea it's a problem.  Tends to be when one group defects, that others also defect.  There is a chance that the bridge doesn't work.  That this all slides, and we do spam each other, and we end up giving up on the whole project.  If it weren't worth taking the risk we wouldn't have tried.

We have not rushed into this bridge thing, we have been talking about it calmly and slowly and patiently for what seems like forever.  We are all excited to be taking a leap, and keen to see it take off.

Yes, security is a valid concern, walled gardens being bridged into is a valid concern, we are trying our best.  We are just as hesitant as you, and being very careful about the process.  We want to get it right.

So if I am in <server1> and I want to talk to <server3> I can just post in the <bridge-to-server2> room and have the message relayed around to server 3 right?

Whilst that is correct, please don't do that.  You wouldn't like people relaying through your main to talk to other people.  Also it's pretty silly, you can just post in your <servers1> main and let other people see it if they want to.

This seems complicated, why not just have one room where everyone can go and hang out?

  1. How do you think we ended up with so many separate rooms
  2. Why don't we all just leave <your-favourite server> and go to <that other server>?  It's not going to happen

Why don't all you kids get off my lawn and stay in your own damn servers?

Thank's grandpa.  No one is coming to invade, we all have our own servers and stuff to do, we don't NEED to be on your lawn, but sometimes it's nice to know we have friends.

<server2> shitposted our server, what do we do now?

This is why we have mods, why we have mute and why we have ban.  It might happen but here's a deal; don't shit on other people and they won't shit on you.  Also if asked nicely to leave people alone, please leave people alone.  Remember anyone can tap out of any discussion at any time.

I need a picture to understand all this.

Great!  Friends on exegesis made one for us.


Who are our new friends:

Lesswrong Slack

Lesswrong slack has been active since 2015, and has a core community. The slack has 50 channels for various conversations on specific topics, the #open channel is for general topics and has all kinds of interesting discoveries shared here.

Discord-Exegesis (private, entry via tumblr)

Exegesis is a discord set up by a tumblr rationalist for all his friends (not just rats). It took off so well and became such a hive in such a short time that it's now a regular hub.

Discord-Lesswrong

Following Exegesis's growth, a discord was set up for lesswrong, it's not as active yet, but has the advantage of a low barrier to entry and it's filled with lesswrongers.

Discord-SSC

Scott posted a link on an open thread to the SSC discord and now it holds activity from users that hail from the SSC comment section. it probably has more conversation about politics than other servers but also has every topic relevant to his subscribers.

Discord-r/rational

reddit rational discord grew from the rationality and rational fiction subreddit, it's quite busy and covers all topics.


As at the publishing of this post; the bridge is not live, but will go live when we flip the switch.


Meta: this took 1 hour to write (actualy time writing) and half way through I had to stop and have a voice conference about it to the channels we were bridging.

Cross posted to lesswrong: http://lesswrong.com/lw/oqz

 

In support of Yak Shaving

13 Elo 16 March 2017 05:31AM

Original post:  http://bearlamp.com.au/in-support-of-yak-shaving/

Part 2:  http://bearlamp.com.au/yak-shaving-2/


Yak shaving is heralded as pretty much "the devil" of trying to get things done.  The anti-yak shaving movement will identify this problem as being one of focus.  The moral of the story they give is "don't yak shave".

Originally posted in MIT's media lab with the description:

Any seemingly pointless activity which is actually necessary to solve a problem which solves a problem which, several levels of recursion later, solves the real problem you're working on.

But I prefer the story by Seth Godin:

"I want to wax the car today."

"Oops, the hose is still broken from the winter. I'll need to buy a new one at Home Depot."

"But Home Depot is on the other side of the Tappan Zee bridge and getting there without my EZPass is miserable because of the tolls."

"But, wait! I could borrow my neighbor's EZPass..."

"Bob won't lend me his EZPass until I return the mooshi pillow my son borrowed, though."

"And we haven't returned it because some of the stuffing fell out and we need to get some yak hair to restuff it."

And the next thing you know, you're at the zoo, shaving a yak, all so you can wax your car.

I disagree with the conclusion to not yak shave, and here's why.


The problem here is that you didn't wax the car because you spent all day shaving yaks (see also "there's a hole in my bucket").  In a startup that translates to not doing the tasks that get customers - the tasks which get money and actually make an impact, say "playing with the UI".  It's easy to see why such anti-yak shaving sentiment would exist (see also: bikeshedding, rearranging deck chairs on the titanic, hamming questions).  You can spend a whole day doing a whole lot of nothings; getting to bed and wonder what you actually accomplished that day (hint: a whole lot of running in circles).

Or at least that's what it looks like on the surface.  But let's look a little deeper into what the problems and barriers are in the classic scenario.

  1. Want to wax car
  2. Broken hose
  3. Hardware store is far away
  4. No EZpass for tolls
  5. Neighbour won't lend the pass until pillow is returned
  6. Broken mooshi pillow
  7. Have to go get yak hair.

So it's not just one problem, but a series of problems that come up in a sequence.  Hopefully by the end of the list you can turn around and walk all the way straight back up the list.  But in the real world there might even be other problems like, you get to the hardware store and realise you don't know the hose-fitting size of your house so you need to call someone at home to check...

On closer inspection; this sort of behaviour is not like bikeshedding at all.  Nor is it doing insignificant things under the guise of "real work".  Instead this is about tackling what stands in the way of your problem.  In problem solving in the real world, Don't yak shave" is not what I have found to be the solution.  In experiencing this the first time it feels like a sequence of discoveries.  For example, first you discover the hose.  Then you discover the EZpass problem, then you discover the pillow problem, at which point you are pretty sick of trying to wax your car and want a break or to work on something else.


I propose that classic yak shaving presents a very important sign that things are broken.  In order to get to the classic scenario we had to

  1. have borrowed a pillow from our neighbour,
  2. have it break and not get fixed,
  3. not own our own EZpass,
  4. live far from a hardware store,
  5. have a broken hose, and
  6. want to wax a car.  

Each open problem in this scenario presents an open problem or an open loop.  Yak shaving presents a warning sign that you are in a Swiss-cheese model scenario of problems.  This might sound familiar because it's the kind of situation which leads to the Fukushima reactor meltdown.  It's the kind of scenario when you try to work out why the handyman fell off your roof and died, and you notice that:

  1. he wasn't wearing a helmet.
  2. He wasn't tied on safely
  3. His ladder wasn't tied down
  4. It was a windy day
  5. His harness was old and worn out
  6. He was on his phone while on the roof...

And you realise that any five of those things could have gone wrong and not caused much of a problem.  But you put all six of those mistakes together and line the wind up in just the right way, everything comes tumbling down.


Yak shaving is a sign that you are living with problems waiting to crash down.  And living in a situation where you don't have time to do the sort of maintenance that would fix things and keep smoulders from bursting into flames.

I can almost guaranteed that when your house of cards all come falling down, it happens on a day that you don't have the spare time to waste on ridiculous seeming problems.


What should you do if you are in this situation?

Yak shave.  The best thing you can do if half your projects are unfinished and spread around the room is to tidy up.  Get things together; organise things, initiate the GTD system (or any system), wrap up old bugs, close the open loops (advice from GTD) and as many times as you can; YAK SHAVE for all you are worth!

If something is broken, and you are living with it, that's not acceptable.  You need a system in your life to regularly get around to fixing it.  Notepadsreviews, list keeping, set time aside for doing it and plan to fix things.

So I say, Yak Shave, as much, as long, and as many times as it takes till there are no more yaks to shave.


Something not mentioned often enough is a late addition to my list of common human goals.

Improve the tools available – sharpen the axe, write a new app that can do the thing you want, invent systems that work for you.  prepare for when the rest of the work comes along.

People often ask how you can plan for lucky breaks in your life.  How do you cultivate opportunity?  I can tell you right here and now, this is how.

Keep a toolkit at the ready, a work-space (post coming soon) at the ready, spare time for things to go wrong and things to go right.  And don't forget to play.  Why do we sharpen the axe?  Clear Epistemics, or clear Instrumental Rationality.  Be prepared for the situation that will come up.

Yak Shave like your life depends on it.  Because your life might one day depend on it.  Your creativity certainly does.


Meta: this took 2.5 hrs to write.

Noble excuses

3 Elo 13 March 2017 11:29PM

Original post: Noble excuses


I was talking to a lady in her 60s who was losing weight, and exercising.  She said to me; "All my life, my husband was an iron man.  I felt terribly embarrassed, like everyone in the room was looking at me and thinking - how could he be with her".  She confided that she wanted to lose weight for completely superficial reasons, really dumb reasons of caring what people thought about what she looked like.  She asked me if this made her a bad person, that she was doing things for the wrong reasons.  We just covered Valid and invalid excuses, the territory of excuses overlaps quite heavily with the territory of goals.  We make excuses and decisions to do some things and not other things because of our goals.  Earlier in the conversation, my friend also shared the usual "get fit, be healthy" attitude that is the more noble reason to be getting fit.

I wouldn't be the first to name this concept.  There is a class of excuse that is known as the noble excuse.  A noble excuse is the excuse for the action that you are making that sounds the most noble of the possible excuse space.  Which is to say; there are often reasons for doing something that extend beyond one or two reasons, and beyond the reason you want to tell people right away.

When I tell my friends I didn't go for a run this morning because I "Don't want to be late for work". That's so noble.  It had nothing to do with me being out late the night before, it's raining, the grass is wet, I have hayfever, I didn't get enough sleep, missed my alarm and woke up late.  No it's all for caring about being late for work.

Also coming in the form of Noble justifications, a noble excuse is tricky because it acts as an applause light.  It tells the guilty brain, "okay you can stop looking now we found out why", it's safe to say that they don't really help us, so much as save face among others or even to ourselves.


Speaking of a noble excuse

"Is that the real reason or is that just a noble excuse"

"Let's not settle on the first noble excuse, what other reasons could there be for these events"

"I wish I could give a noble excuse for being late, but the truth is that I have a bad habit of leaving home late and missing the bus.  Next week I will be trying out setting my watch to a few minutes faster to try to counteract my bad habit."

"That's a pretty embarrassing mistake, is there a noble excuse that we can pass on to the client?"


Dealing with a noble excuse

Not all noble excuses are bad.  If you notice someone making a noble excuse, it usually doesn't hurt to double check if there isn't another reason behind those actions.  There's not a lot to understanding noble excuses.  It's about being aware of your excuses and connecting them back to their underlying goals.

Think carefully about the excuses you are making.


Meta: this took an hour to write.

Open thread, March 13 - March 19, 2017

2 Elo 13 March 2017 03:46AM

Notes for future OT posters:

1. Please add the 'open_thread' tag.

2. Check if there is an active Open Thread before posting a new one. (Immediately before; refresh the list-of-threads page before posting.)

3. Open Threads should start on Monday, and end on Sunday.

4. Unflag the two options "Notify me of new top level comments on this article" and "

View more: Next