mdlbear: blue fractal bear with text "since 2002" (Default)

We got up reasonably early on Wednesday, were on the road by a little after 9am after a huge breakfast at Black Bear Diner, and arrived at the Starport in time to order pizza and chicken wings for dinner. Not staying again at the Grants Pass Travelodge -- the 2-bed rooms are tiny, and even the ground floor isn't really scooter accessible. There's just enough room between the bed and the wall to drop my CPAP into.

Og has done yeoman's work on the living room floor; it looks terrific (as long as you don't look at the edges, which are ragged). Liz and Devon did great work packing, though they apparently didn't realize that we wouldn't want to use paper plates and plastic forks for the rest of the time we're here. Normally, you save things like the kitchen and bathroom for the last minute.

I spent most of Thursday and yestday packing. Thursday mostly the office; Friday included taking down one set of the garage shelves. I'm pretty sure now, looking at them, that the end bays were assembled on their sides and tilted up. I think I'm going to leave one set here.

I still have a huge amount of triage and packing to do, even though most of it is almost certainly junk.

Links, as usual, below in the notes.

raw notes )
mdlbear: blue fractal bear with text "since 2002" (Default)
raw notes )

I seem to have more notes than I usually do at a con. Possibly due to the fact that I'm spending more down time. The lobby (where the bar is) and mezzanine (where the programming is) are connected, and incredibly noisy. That's probably a large part of why I ran out of spoons around 10pm and went upstairs to bed. That, the fact that something in dinner wasn't sitting well, and that I'd just spent two hours in the room waiting for the hotel to clean up the mess made by the overflowed toilet.

The apparent problem with the phone was just pilot error -- it's cordless, and I didn't press the talk button. Not so much as "idiot bear" as totally overloaded and flustered, and perfectly willing to believe that One More Thing was going wrong.

... so I didn't get to any of the concerts.

I did get a couple of nice strokes, though -- one person told me that one of his coworkers has a copy of my book on his desk, and another told me that she'd used my River posts about the care and feeding of geeks to understand and deal with a coworker. Those felt good.

Lots of people seem to know me by name who I don't recognize at all. "He's losing his memory and some of his hair"? That's somewhat disturbing.

It was a good day for most of it, I ended the day feeling seriously down and drained. This was almost certainly a simple matter of being out of spoons rather than depression -- I'm ok now. I think it's hard for me to distinguish physical exhaustion from sensory overload from emotional depression, though. That's something I'm going to have to work on.

A couple of links.

mdlbear: blue fractal bear with text "since 2002" (Default)

If I'm obviously frazzled and desperately looking for something valuable that I'm afraid I've lost, DO NOT say something to the effect of "It's all right." It is manifestly not all right, and you will get snapped at. I don't want to snap at you.

mdlbear: blue fractal bear with text "since 2002" (Default)

It's been a while since I posted anything with a significant amount of River content; little things like life, the universe, and everything have been conspiring against me. I'm sorry to disappoint you again, but it seemed as though this was a good time for a sort of re-introduction and status report before we continue our journey.

The River posts started out as a journey of personal exploration, concentrating on mental states, emotions in particular, interpersonal communication, and relationships. Along the way they seem to have acquired a second theme of advice, primarily for geeks like me and people in relationships with geeks. (I'll get into definitions in a little while.) How this geeky old bear found himself in the role of slightly bemused relationship counselor is a longish story that has yet to be told in full, but you'll find bits of it in the archives if you're curious.

There seem to be three main types of River posts. There are, of course, general posts that have a brief mention of a River-related topic -- those usually just get the tag. There are the ones that report on, and usually analyze, a specific incident or event from a riparian point of view -- often these have the phrase "on the River" in their title. And finally there are the more carefully-considered posts, of the sort [livejournal.com profile] cflute calls "The Mandelbear waxes philosophical", which usually have titles that start with the "River:" keyword.

At any given time I may have a half-dozen or so posts in various stages of writing, and another dozen in the form of a title and a few notes. They often stay in this state for months, until I either get tired of beating on them, or they get triggered by some event, usually on my friends list, that makes them suddenly relevant.

Definitions:

Although there are plenty of terms I use in a somewhat non-standard sense here on the River, the only two I want to highlight here are geek and human. I believe I first started using the pair of them in a technical sense in a post titled Humans are from Earth, geeks are from Saturn.

Geek
This is intended as a humorously self-deprecating, fairly general term that covers anyone who, like me, has trouble relating to and getting along with "normal" people. It covers a fairly wide range, including aspies, people with adult ADD, loners, and in some aspects people who are simply terribly shy. Geeks often have an easier time relating to computers than to people; some of my earlier posts have mentioned "hackers" in this connection.
Human
This is meant as a less disparaging term for "normal" people than things like "neurotypical", which is common in the Aspie community.

I'll note immediately that I'm well aware that many people -- probably including most of my readers, fall somewhere in between the two categories, or have aspects of one or the other in different situations.

Sub-tags:

Here are the tags commonly used for River subtopics. This set changes over time, and posts will occasionally have tags that are used more widely.

c9n
Calibration -- getting or soliciting feedback or corrections (outside of LJ -- inside LJ I'd use "query"). You may have met the practice of using a number to stand for the number of omitted letters in "i18n", the common abbreviation for "internationalization".
comm
Communication
def
Definitions. Often also have "Defining my terms:" in the title.
human
The whole "being human" thing (usually in the context of my abject failure at it).
meta
A post about posting. This post, for example.
np
N-person relationships (where n>2). The definition of np-complete and np-hard are left as an exercise for the reader.
psa
Public Service Announcement. Something I want people to know about me.
psych
Psychology, including mental states, psychopharmacology, and so on.
query
Questions of the readership, often for calibration purposes.
rel
Relationship

Books?

The River seems to have spawned some related writing projects. The first, thought of a couple of months ago and introduced in a post titled The River: it's not just a tag anymore, was the comparatively straightforward idea of turning the first year's worth of posts and some selected comments into a book, A Year on the River. It will require some serious editing, of course.

The second, and more recent (as in just this week), is the idea of writing a pair of somewhat more organized self-help books, tentatively titled Relating to Humans -- A Manual for Geeks and Relating to Geeks -- A Manual Mostly for Humans. I envision them being printed back-to-back, like one of the old Ace Doubles. Anybody else remember those? It would make sense because, as I've noted above, many people fall somewhere in the middle. And, of course, because geeks have most of the same problems relating to other geeks that humans do.

(The initial phrase, currently "Relating to", is up for grabs; additional possibilities include "Living with" and "The Care and Feeding of".)

Naturally, both of these projects will start out as wiki-like websites, so that I can get some help -- I'll need it.

mdlbear: blue fractal bear with text "since 2002" (Default)

This came out of an incident toward the end of this weekend's trip.

Snapdragons:

The snapdragon is a pretty flower with a fierce-sounding name. It looks as though it's set up to eat insects, but in fact all it wants to do is hold on to them long enough to deposit some pollen on them to send to the next snapdragon they visit. But sex by proxy is an entirely different story.

The snapdragon effect

It turns out that [livejournal.com profile] cflute, who we were visiting over the weekend, is even more sensitive than I am to what she calls "crosstalk". If she's trying to talk or write, words directed at her will break her concentration. We were engaged in a rather complex and stressful project when [livejournal.com profile] pocketnaomi derailed C's train of thought and got "snapped at". She was, understandably, hurt and upset, and said so. This got C angry in turn; N left the room rather than let it escalate. (edited 0719t1535 in response to a correction in comments.)

It turns out that N is at least as sensitive as Colleen is to phrasing and tone of voice. It's a hypergolic mixture. And C doesn't have the benefit of 30-odd years' experience with this problem.

When it happens between me and Colleen the usual result is Colleen bursting into tears, but it's the same thing. I wrote this up back in February in this post, where I attributed the phenomenon to the confusion of being yanked out of a state of flow, but it seems to be a lot more general than that.

Whether you're a geek or non-geek, whether you're in flow or just concentrating on something tricky, there's that moment of confusion when you're jolted out of your concentration by a chance remark, an innocent question, or even a vitally important but ill-timed message. During that moment, if you say something, there's going to be stress in your voice. You're going to snap at the source of the interruption.

And, especially if they love you, the source of the interruption is going to interpret your tone of voice as angry. Both effects, the snap and the reaction to it, are near-instantaneous and totally automatic. It's all over before either person has a chance to collect their wits and think about what they're saying or hearing.

In most cases, you didn't even notice. What you said and how you said it didn't even register on a conscious level -- you were thinking about something else, after all. The first thing you notice is the reaction.

All you can think to do, once you get that totally unexpected and, to you, totally unfair and unwarranted reaction, is explain what you think happened. All your poor partner/spouse/lover/friend/kid can think is that you're still angry and giving them a dressing-down. Don't go there: you're making things worse. Apologize as quickly as you can, and shut up.

The snapdragon solution

I'm suggesting the code-word "snapdragon" for this -- it's memorable, and somewhat descriptive. "Are you being a snapdragon?" "Sorry; I was a snapdragon there." Actually, just "snapdragon" works fine if you both know the code-word; Colleen has already used it that way this evening, less than an hour after I introduced it.

It'll work in both directions: the first one to notice a snapdragon interaction gets to tag it. Once you've confirmed that it was a snapdragon, you can -- and should -- drop the subject and move on. Preferably move on to something like a kiss or a hug, along with pride at having successfully averted a serious breakdown of communication.

I've already mentioned "Basingstoke" in a similar function, but it doesn't seem to have stuck in this context, perhaps because it's neither as memorable nor as specific. I think I'l save that one for use in the rather different situation where my disagreeing with something Colleen says comes across as not listening.

Just as a linguistic aside, my reaction at being accused of snapping at Colleen used to be something like "I didn't snap at you; you startled me and I couldn't control my voice." Rubbish. I snapped at her. I might not have been angry when I snapped, but "snapping" is the correct word for what I did. Sorry about that, Love.

mdlbear: (hacker glider)

Hackers are used to working with computers, which are fast, accurate, and extremely literal-minded. A hacker knows, deep down in his guts, that if something is wrong with the program he's writing, it's his fault. The normal human mechanisms of blame-shifting and denial don't come into play at all: the only thing to do is fix the problem and move on.

This means that if you can point out something that the hacker in your life is doing wrong, there's an excellent chance that he'll get to work on it. My father provided a good example of this: he discovered that he didn't have anything to talk about besides technology. That's fine with other techies, but not very helpful at cocktail parties. Someone else (um... \me looks in mirror and clears throat) might have stuck to his own kind, or crawled off into a corner to read.

Dad, instead, made himself an expert on wine, with a sideline in hotels and restaurants around the world. By the time I was in high school he had a notebook with not only the best places to eat and places to stay in hundreds of cities, but which rooms had the best view.

I do have to warn you that there's a downside to dealing with machines a lot of the time: it's safe to yell at a machine, because it has no feelings to hurt. There's anger there, but it's not really directed at the machine -- it's really directed at himself. How could he possibly have been so stupid? A few minutes later, of course, he'll figure out exactly how, and by the end of the day he'll be happily telling the story of his own stupidity, and his clever fix for it, to anyone who stands still long enough to listen. Just something to watch out for.

(Side note: I'm going to change focus of this series from geeks in general to hackers/computer geeks, because that's really the only subspecies I'm familiar with.)

Flow

2008-02-04 09:24 pm
mdlbear: (hacker glider)

This will probably, at some point, expand into a "Care and Feeding of Your Geek" article; for now it's just some notes on flow and how it relates. the Wikipedia article defines flow as "the mental state of operation in which the person is fully immersed in what he or she is doing, characterized by a feeling of energized focus, full involvement, and success in the process of the activity." It's often described as "losing oneself" in the activity.

There's more. Go read it. I'll wait.

Most geeky activities -- programming, gaming, art, music, dance, reading -- are enhanced by the kind of active concentration that characterizes flow. Flow, in turn, is often one of the beneficial side-effects of Asperger syndrome, a mild form of which is common among geeks.

There are three things you have to know about flow and your geek.

First, if your geek is concentrating on something, you aren't there. Neither is he. (I'm going to use "he" to refer to your geek because I'm male, and this is partly directed to my keeper wife; adjust as needed.) Your geek may seem to be present; he may even be able to carry on what appears to be a brief conversation. Don't be fooled. Almost all of his mind is lost in what he's doing. Don't be surprised if he doesn't remember a thing you said afterwards.

Second, getting yanked out of a flow state hurts. If you break your geek's concentration, expect to be snapped at. It has nothing to do with you: he'd snap at a dog, his mother, or a phone call saying that he's won the lottery. The sensation, if you haven't felt it yourself, is a lot like being awakened from an exceedingly pleasant dream by a loud noise that can't be immediately identified. Your geek may not even remember what he says at that moment -- he'll be sorry about it, but he really didn't know what he was saying. You may have noticed him walking into lampposts while reading a book, too.

Third, however, is that flow is the reason why geeks often make surprisingly good lovers. Consider the implications of having 100% of his attention on you. If you ask him what he's thinking about, he might not be able to answer. If you ask him why he thought to scratch you just exactly there where you needed it, he probably won't be able to answer that one either. If you ask him to stop, ... never mind; you probably won't want to.

mdlbear: (technonerdmonster)

From this post by the ever-fascinating [livejournal.com profile] cadhla we get a link to The Nerd Handbook. While not quite an operating manual for your friendly local Mandelbear, it comes pretty close.

I'll write one specifically for me in my copious spare time.

Most Popular Tags

Syndicate

RSS Atom

Style Credit

Page generated 2025-06-02 04:06 pm
Powered by Dreamwidth Studios