I’ve known for years that I’m not very fond of the thing commonly referred to as “teasing”, or more technically “casual interpersonal antagonism”. I made that term up. But there’s something helpful in thinking that there could be technical terms for stuff like this. Another technical term is “friendly countersignaling“. It seemed people were trying to justify saying mean things by saying “well I didn’t really mean it” but it seemed that often they did mean it.
I realized this way back when I had my first break-up at age 16. My partner at the time really liked a certain kind of teasing that I found very aversive (for example, saying “you’re weird” in a way that made it sound like this was a bad thing) and this was one part of what made things tense enough to prompt a breakup (although maybe it just exacerbated existing tension?). I don’t blame her: at the start of our relationship, a year or so prior, I’d actually been quite teasy myself, but I think that that teasing (which was fairly flirty I guess) itself came out of a lot of insecurity and fear that I had had at the time. Like I was trying hard to pretend I didn’t like her because I was afraid she mightn’t like me. Whereas once we’d been dating for awhile that didn’t really make sense, on my end.
Anyway, enough about Malcolm’s early love-life. The point is that I had an aversion to teasing, not just abstractly but from a specific instance of it being problematic. I even had a model of myself as someone who didn’t like teasing, and I warned some later romantic partners about it going into the relationship. But I didn’t really think much more about why I didn’t like teasing: it just seemed like the natural state of affairs.
Until this summer.
John Shotter, in More than cool reason: ‘Withness-thinking’ or ‘systemic thinking’ and ‘thinking about systems’, writes about the difference between “aboutness” and “withness” thinking. The former tries to look at the world objectively: to place oneself outside of what’s being looked at. The latter includes the self and its relationship to the whole in the sense-making.
He describes how with complex situations, which includes many social ones, we need to use withness thinking, because we don’t just need to learn new things but we need to become something new. In these situations, we’re changing not just what we think about but “what we think with”… how we relate to our situation.
Hence these kinds of changes cannot be produced by following intellectually devised plans, procedures, or protocols; they cannot be done, intentionally, by people taking deliberate actions—this is because the coordinated execution of planned actions depends upon all concerned already sharing the set of existing concepts relevant to the formulation of the plan, thus all new plans depend on old concepts – the process results in the “continual rediscovery of sameness.”
This is something that makes a lot of sense to me, in many ways. I’ve written before about the idea that some things have to be learned by abstracting from experiences, rather than by being told something or otherwise following a series of steps.
It’s also something I find kind of scary. I found it scary two years ago—I know this because I wrote so in the margins of the article when I first read it then.
Tonight I realized why.
» read the rest of this entry »
At burning man this year, I spent a day exploring that question, from the inside and from the outside.
“What’s it like to be you?” I asked someone sitting at the Tea House at my camp. They said something like, “It’s awesome. My life is really great. I have all of these really good friends…” and I said “Sure, sure, but what’s it like?”
I was trying to understand, I guess, what the texture of his qualia was like. (Qualia = “an unfamiliar term for something that could not be more familiar to each of us: the ways things seem to us”(wikipedia)) I was having this feeling that other people were just figures in my dream, or just characters in my story, and I think this was in part an attempt to break out of that.
I spent a few hours at the Tea House, talking with friends and strangers, trying to get glimpses into what the plots of their stories looked like, and sampling my own experiences as well. I ran into Brayden, one of my campmates, around the start of this, who told me that he was heading out. I ran into him again, hours later, just before I was heading out, and he said he was going to go sleep.
I spent a moment being present to the reality that he had had his own story happen in the space between those two tiny interactions, and that our plots had just intersected momentarily.
After I left camp, I found myself reflecting that the “What is it like to be you?” question, while pointed and interesting, wasn’t the only way to get clues about the texture of others’ experience. “How are you doing?” when asked with the right kind of tone, could actually generate some windows into the other person as well. Also, of course, off-hand remarks that people make, if you’re paying attention.
Part of my mission for that day was » read the rest of this entry »
I once caught myself whistling.
I had done something to someone, that I really regretted, and I felt sick about it. I kept replaying the scene, wishing I’d done something different. Over, and over.
Then I was working on math homework, and just kind of distracted myself from being a person interacting with other people altogether. It was just me, and the symbols, the logic.
After the math homework, I was on my way to meet up with people to go for a run, and I caught myself whistling some sort of cheery tune. I was shocked: “Malcolm, you can’t be whistling..! You’re supposed to be all upset about this thing you did!”
I came so close. To believing what I told myself. I very nearly threw myself back down into that pit of despair and angst and regret and nausea. But then I realized I didn’t have to. That me stewing over what I’d done wasn’t helping anyone at all.
So I kept whistling.
My parents had told me, since I was quite young, that I could choose what emotions I felt in response to a situation.
Raise your hand if you’ve practised mindfulness before.
Mindfulness [meditation], as probably most of you know, is the practice of focusing your attention on (usually) your breath, and when your mind wanders, bringing it back. You’re training your ability to deliberately influence your subjective experience. You’re training your ability to not be distracted, and to recover from distraction.
But how are you doing this? You’re sitting on your cushion, in your quiet room… practising not being distracted by… well, nothing. I mean, your own thoughts, sure. But you’re not really trying to use your brain for anything, so this is pretty crude: all thoughts get set aside. This is maybe level one mindfulness: a good foundation, but not that directly applicable to everyday life.
What can you do with it? What would applied mindfulness look like?
How could you train these skills in contexts more like the ones in which you’ll actually use them?
School taught me to write banal garbage because people would thumbs-up it anyway. That approach has been interfering with me trying to actually express my plans in writing because my mind keeps simulating some imaginary prof who will look it over and go “ehh, good enough”.
Looking good enough isn’t actually good enough! I’m trying to build an actual model of the world and a plan that will actually work.
Granted, school isn’t necessarily all like this. In mathematics, you need to actually solve the problem. In engineering, you need to actually build something that works. But even in engineering reports, you can get away with a surprising amount of shoddy reasoning. A real example:
Since NodeJS uses the V8 JavaScript engine, it has native support for the common JSON (JavaScript Object Notation) format for data transfer, which means that interoperability between SystemQ and other CompanyX systems can still be fairly straightforward (Jelvis, 2011).
This excerpt is technically totally true, but it’s also garbage, especially as a reason to use NodeJS. Sure, JSON is native to JS, but every major web programming language supports JSON. The pressure to provide citable justifications for decisions which were made for reasons more like “I enjoy JavaScript and am skilled with it,” produces some deliberately confirmation-biased writing. This is just one pattern—there are many others. » read the rest of this entry »
It’s all too easy to let a false understanding of something replace your actual understanding. Sometimes this is an oversimplification, but it can also take the form of an overcomplication. I have an illuminating story:
Years ago, when I was young and foolish, I found myself in a particular romantic relationship that would later end for epistemic reasons, when I was slightly less young and slightly less foolish. Anyway, this particular girlfriend of mine was very into healthy eating: raw, organic, home-cooked, etc. During her visits my diet would change substantially for a few days. At one point, we got in a tiny fight about something, and in a not-actually-desperate chance to placate her, I semi-jokingly offered: “I’ll go vegetarian!”
“I don’t care,” she said with a sneer.
…and she didn’t. She wasn’t a vegetarian. Duhhh… I knew that. We’d made some ground beef together the day before.
So what was I thinking? » read the rest of this entry »
Some things you don’t learn by being told (or telling yourself), you learn by organizing your experiences.
A few weeks ago I was talking with a friend, Ruby, over skype. Our conversation drifted to letters one might send to one’s past self, from say 1-2 years ago. Aside from the obvious tip-off’s about stock prices or romantic inclinations or lacks thereof, what would be useful to say? Ruby proposed sending his past self a list of books to read sooner. I though that was probably better than lots of other approaches (in part because it lets you send more information than you could possibly fit into a letter) but it seemed to me like there was a non-obvious challenge to doing that effectively, related to experience. There are some books that are broadly pretty mindblowing, but I’ve found that often when books really rock my world it’s because I’m particularly ripe for them at that moment. I think that trying to send a revelation to your past self, if you weren’t ready for it, might have a bit of an Archimedes’s Chronophone effect, where everything comes out sounding kind of obvious rather than insightful.
A second story: I was talking with some friends about Robert Kegan’s Constructive Developmental Theory. The structure of CDT is about shifting parts of your experience from being [thoughts you are subject to] to being [thoughts you can take as object, i.e. think about]. I’ve blogged about this here. Its content is a set of five specific subject-object stages in how people view themselves, ideas, and other people. Anyway, one of the people I was talking to has a 10-year-old daughter, and he was wondering if I had advice on how to help her go through the shifts faster. After noting that that wasn’t necessarily a good idea (I mean, it could be, but it might make her feel more distanced from her peers), I remarked that the process is complex and it’s not enough to just teach her certain things or to get her to do certain other things.
Because each subsequent shift in Kegan’s system represents not just new knowledge or understanding, but an entirely new kind of order applied to the level below. » read the rest of this entry »
Context: this was a very stream-of-consciousness post, tapping into something I had just learned when I wrote it, yesterday. I don’t necessarily think that what I suggest here makes sense for everyone. But it spoke something really valuable to me, and I suspect there will be others who deeply appreciate it as well.
Today, my friend Matt and I found ourselves in a particular head-space as well as an intense and exciting conversation where we were speeding up, and were continually needing to remind ourselves to take a breath. I found each breath so powerfully pleasant that it made for a really interesting feedback loop. Note that all uses of “breath(e)” here refer to the act of consciously, mindfully, taking a breath.
I’m going to invite you to do that now, as you read this.
Inhale.
Exhale.
The “take a breath” piece of feedback is part of a much larger energy-awareness thing I’ve been working with for a long time—it’s connected with againstness and so on as well. Essentially, I’ve been working to overcome an experience I’ve sometimes had of myself where I’ve gotten slightly caught up in my own thoughts and slightly worked up, while interacting with people, in ways that have felt disconnecting and unpleasant for them. And in general, when people have given me feedback about this, I’ve had largely positive reactions in response.
What I realized today though, was that it could be even more positive. Or perhaps we might say positive “sooner”.
This is a topic for another post, but I want to briefly present a model I’ve been using for awhile to capture the process of human interaction with the world.
(This post starts with a technical example, but it’s not about the technical stuff so don’t worry about trying to understand the details.)
A friend of mine reached out to me earlier today, with a question about trouble she was having while coding something. She’s working in NodeJS, which I’m really familiar with since it’s what my productivity app, Complice is built on. “I’m having this problem with doing GET-requests… I can’t get them showing different things based on the url…”
A few sentences later, when I still didn’t really understand her problem, I said, “Hang on. Let’s back up—what is the user trying to do here? Like what’s the point of this page?”
She said something like, “so it’s like, they’re trying to load the data, but when they bring up the page, I can’t specify exactly what data they want.”
“Nonono, back up. I still don’t know what problem you’re solving for the user of this system. What’s the user trying to do?”
When you’re stuck on (or in) a problem, it can be easy to end up with a really narrow view of what you need to do to solve it, becoming overfixated on a given intended solution and focusing all of your questions around that solution, rather than around the original problem. This can happen on the scale of a day’s debugging, or on the scale of an entire startup.
It took me several more times of asking before I finally got my friend to back up far enough to talk about the situation from the user’s perspective, and once she did, she was suddenly like WAIT! and then came back a few minutes later with the solution.
As I had predicted, the biggest hurdle to her figuring out this problem was an assumption that she was making. I actually still don’t know what that assumption was. It would have also been possible for this story to end with her stating one of these assumptions, which I would have then overturned. But she ended up realizing it all on her own.
Stack Overflow, a Q&A website for programmers, calls this whole thing the XY Problem: when the asker asks about their attempted solution, rather than about the original problem they didn’t know how to solve.
And this isn’t unique to programming.
