Stutter, stutter.

[azurelunatic]

I can't talk. I stutter. I write the same words I would say on the board. I know what the names of the things are. I can't say the words that are the actions, how they play with each other and change each other. They dance together, and I can say how they work with the arrows, but the words don't work.

They modify.
They update.
Change.
Flag.
Return.

Why can I not say that because it changes a bool, it does not have to return? How can I say this in English? The query returns a value. Not the update. Unless we want to know that the update had been successful. Only then.

Comments

[boojum.livejournal.com]

"[B]ecause it changes a bool, it does not have to return[.]...The query returns a value. Not the update. Unless we want to know that the update had been successful."

That's fairly explanatory, to me. You could reword it to be complete sentences, which would be less abrupt: "It doesn't have to return a value, because it's not querying anything. Unless we want an error code returned to know if the update was successful, it can just return void." I don't think there's a specific word for it.

Are you being N%?

[azurelunatic]

Yes. I am.

Reword is not my vocabulary to do it. Still building that. That's Azz's thing. Not mine. Azz communicates with words. Dagger fights with them. I don't, yet. Building things with them. Just know the few words.

[iroshi.livejournal.com]

You're very young for words, honey, and why are you doing the homework? Shouldn't Azz be doing the homework??

[azurelunatic]

Programmer. My job. Talk with them, her job.

Re:

[iroshi.livejournal.com]

Ah, gotcha! You know, that makes so much sense. But then, y'all usually do.

So then, the writing it out in English then is equivalent to talking with them. You should write the code and then make *her* write the paper, or the commenting of it.

[azurelunatic]

No. We do fine writing. We can switch when writing. Easy.

Trouble *talking* in person. Explaining. Can't switch easily realtime facetime. In lab together, all of us. Working together. Five people in group. Am one of the five. The other lady, the three guys. I am one who 'gets it'. I am one who has to work out the theory into our drawings and concepts, and we must translate what I see into their language.

Can't switch fast realtime when working. Hard. Could if emergency. Not when working.

Re:

[iroshi.livejournal.com]

Ahhhhh. Hrm. Interesting. Wonder if you could code some sort of resource-sharing into the central system. N% running the coding, Azz doing the translating and running the mouth only. I *know* you guys can all be aware and think simultaneously, so all it is is a physical control-sharing issue. One of you runs the hands, and the other one runs the mouth. You need to install output ports!

[azurelunatic]

http://www.livejournal.com/users/azurelunatic/2029768.html?thread=2811848#t2811848 --

That's only going to be helpful if *I* actually understand what she's thinking about. If she could translate it into words easily, then I'd be able to understand it and output it with no trouble.

As it is, the proposed solution would result in something along these lines, which is actually fairly close to what's happening now:

Me (with mouth): "I have no idea what we're doing, but I think this is the answer to all the issues we've been having trying to get this to work."
Her (with hands): *draws complex diagram, then spells the procedure out in numbered steps, complete with arrows pointing at what actions are taken and what they do, with amusing verbs detailing how it is done.*
Me (with mouth): "So, evidently, we, um... Let us finish drawing this first."
Her (with hands): *proceeds to take fifteen minutes and finish diagram*
The rest of the group: comments on our prowess with programming, and how when we're in the real work world with a real manager, they're going to ask me to explain something, I'm going to get tongue-tied and take over their whiteboard, much to their surprise.
Her: tunes them out
Me: gets grumpy with her for taking over the ears, because I was trying to listen because it was amusing
Her: internally informs me, "I am FOCUSING!"
Me, after she finishes: "Ah. Evidently this is the object, these are the methods, these are the attributes, and here's what they all do."
Them: "Ahhhh. I think I see. ...Weren't you worried you'd break your neck doing that somersault? The floor's really hard in here."
Me: "Um... hehe... I turned a somersault? Hehe...."

[azurelunatic]

Programming is actually not my skill set. It seems to be hers, much to everyone's surprise but hers. The trouble lies when she has to work in a group.

We even walk differently when we're her.

Re:

[iroshi.livejournal.com]

Oh, her coding doesn't surprise me at all, once it was pointed out to me what she was doing. The *question* she asked confused me.

[azurelunatic]

We either have to teach her how to interact smoothly, or we have to be able to switch seamlessly when she's busy working.

Trouble is, she's the one who can wrap our mind around it. After *I* understand it, I can explain it... but when she's the only one who understands it, she has to be the one who explains it to the group.

Since I don't think switching out would be viable, we're working on how to get her to interact with others a little more smoothly. Already there has been a huge improvement from last week.