Evan J Palmer's Blog

A blog about learning (code, improv, film and, anything else).

Month: November, 2013

Examples of Context Switching

poison cup challenge

Context switching is bad – try to do it as little as possible if you want to be productive and really benefit from Kaizen.

What I’m talking about when I say “context switching” is changing what your brain is focusing on. The more often your brain has to drop out of “The Zone” and switch into something then back to the original task, the more engery you’ll burn and the harder it’ll be.

So the typical context switch I’m talking about is when you’re at work, and you’re deep into the Henderson Account and it sucks. You really don’t care about The Hendersons or their accounts, but The Man buying your lifeforce so you have to do it. It’s boring and you remember that movie with… what’s his name… it was his first movie… the budget was like $7000 oh yeah, it was Primer. Has his new film come out yet – quick Google and your mind is no longer immersed in the Henderson Account, but is thinking about a cool movie. The context has been switched and you’ll need to exert effort to get back up to speed.

So this is a thing that you should try not to do. Which is easier than it sounds.

Anyway, I’ve been thinking recently about different types of context switches that happen to human beings. Firstly, we have the mind wandering one, which I talk about above. Here are a couple of other examples, that I think of as context switches.

When you’re working on something almost every alt+tab is going to be a physical manifestation of a mental context switch – whether you’re checking emails or Reddit.

Reddit, Instagram etc- flicking between little images 
So you go to Intstgram or Reddit or Facebook and you’re greeted with tonnes of little snippets of information that is generally not related to each other. You’ll see a picture of a cat, then a status about Cheryl’s boy trouble, then a photo of Mark at a party, then a video of a guy skating. All these amazing unrelated thing are little context switches that make your brain expel energy … and don’t really give you much benefit.

Working on a large project or little tasks
At your work do you generally have a big project to sink your teeth into or lots of little projects that take up your day. I am proposing that the poeple with the larger projects are more useful to the company and are gaining skills at a faster rate than those who are doing smaller jobs, and I put this down to context switching.

Changing jobs and careers
Do you change jobs regularly? Or even careers? I suggest that the more you do this the more energy is expelled making the switch and the more slowly you’ll be gaining useful skills. I’m not suggesting you stay in a job or career you hate, nor am I suggesting we work for the same company our entire lives. What I am thinking is that maybe we should think, until I can do a  job with something like an 80% efficiency, I should not look for more work. Or, once I feel I haven’t learnt anything new for a while, it’s time to move on. Rather than “screw this, too hard” change jobs.

Yeah, that’s all. This is just opinion. Not sure if there’s any real truth in it, but it’s worth considering how this concept could also be applied to sports and physical training. Do you think this could be applied to relationships as well? Is being friends with someone for a long time better than bouncing between groups of friends? Do you get more out of being with the one person for a long time, or having shorter relationships?


ASYNC as a parameter


Just a small, useless thought I had today regarding using async as a parameter – for example in an asynchronous jquery ajax call:

  url: "file.php",
  type: "POST",
  async: true

Considering the word “asynchronous” is the antonym of its root “synchronous” – it means, “not synchronous” – shouldn’t we use “sync” and invert the defaults? I mean, you would never give any other parameter or method a negated name. You’d never see this for example:

public void UpdateStatus(bool unsuccessful){ ...


public bool DetermineRecordIsNotNew(RecordType record){...


public class Performance {
string Name { get; set; }
DateTime StartDate {get; set;}
bool IsNotCancelled {get; set;}

Anywho, that’s what I think.

I also don’t think that asynchronicity should be true as a default in most cases either.

Meh, whatever.

How does it feel, like?

ChemicalFuckinBrothers 905

I recently did a small weekend course with Jason Chin – a cool IO improv guy from Chigaco.

He taught us a bunch of really interesting stuff, but there was one exercise we did that I thought was particularly useful. I don’t know if it has a name, but I’m going to call it “How Does It Feel, Like” (HDIFL).

Now, the purpose of HDIFL is to cut past the leading crap at the beginning of a scene and cut right to the emotions between the two players – Shoot the Grandma, as Steen would say. We did the exercise a lot and Jason really pulled us up on it when we didn’t hit the nail on the head.

To play HDIFL It’s straight forward. Get two lines of people, two people walk to centre stage. Person 1 says a line – anything relatively meaningless will do. The second player has to say how that line makes them feel about the other player. Eg:

“I brought you some cheese”
“That makes me feel happy that you remembered my birthday”

“I have a two camels”
“That makes me feel angry that you don’t care about animal rights like I do”

This is so important, because it sets the stage for some real conflict.

Speaking of conflict. When you choose the “correct” emotions, Jason pointed out that we tend to have a dramatic, real scene. If we choose the wrong emotion, we can have a more comical scene. So for example:

“My grandma is dead” + “That makes me feel sorry for you” = a dramatic scene.


“My grandma is dead” + “LOL that makes me feel happy, let’s do a small dance on her grave” = a comedic scene.

It’s worth noting that Jason recommended that for beginner players, it’s cool to just say how you feel: “That makes me feel sad” or “That makes me feel happy” is okay for a junior player. The important part is being affected. Once we get the it stuck in our heads that we need to be affected, then we can move on to saying the emotion AND showing it. And eventually, we’ll be so good at showing it, we won’t need to say it as well.