Wednesday February 18, 2009

I know someone who’s looking for a fulltime remote coder for a job he swears is not tedious. If you know anyone really good, let me know.

I got my secret entry code (not the same as “code” in “coder”) for the Expert Reviewer gig, but fortunately there’s nothing there for me to read yet. I say “fortunately” because I really don’t have time right now. I also got the score for the new arrangement of “When I Survey the Wondrous Cross.” And a passel of articles to proofread and review for a new local online magazine. And a new site architecture for the website of the Rabbi I was telling you about. Read his seriously thought-provoking article about heaven if you need a good read this morning.

I’m not sure what I need this morning besides more sleep. I stayed up late last night chatting with a client. I’d gotten home after Tuesday class and done a little bit of work, and was chatting with him about it, and somehow the convo on donation buttons turned into an actual conversation.

Also, when Janalisa showed up for our walk yesterday, I was at a client meeting which had mysteriously morphed from site architecture to a generalized comfort session. While it is easy enough to say, “Okay, then we’ll just remove those extra navigation elements, and I have another appointment now,” it’s harder for me to walk out on someone who is sharing her hopes and fears.

In the course of discussing the need for a good coder last night, I incautiously trotted out my view that coders (one of the varieties of computer guys which you might describe as IT) aren’t sociable and that’s why I don’t know any. This is of course mere stereotype. But if it were true, it might be because any hints of sociability can so easily evolve into actual friendship, and then how would you ever meet that deadline?

Nope, the best thing is to keep your head down and your fingers on the keyboard.

This is also what our church organist does. We thought initially that he was desperately shy, but later we decided that he just doesn’t want to get sucked into friendships, because he has no time.

I’m talking this morning in class about conclusions. It can be very hard for people to end their writing. I notice this in people unaccustomed to public speaking. They get up and start talking, and then can’t figure out how to end, so they keep rambling on. It happens in writing as well. Students get to the end of what they have to say and then decide that they have to write a conclusion, and they end up with something meaningless that says, “I know I’m supposed to have a conclusion.”

At xanga, this doesn’t happen, even when your post is entirely composed of sleep-deprived rambling like this one, because you can always just say, “Time to get ready for work! Gotta go!”






3 responses to “Wednesday February 18, 2009”

  1. chanthaboune Avatar

    I once had a teacher who recommended that you write out the central work first, then go back to write the intro and conclusion.

    At the time I had raised my hand and said “Isn’t that cheating? You have no parameters, you can just write whatever and later pretend like that’s what you meant to write.”

    Clearly, I always work front to back as it were.

  2. ozarque Avatar

    I second the recommendation of chanthaboune’s teacher. That’s absolutely the way to do it.

  3. fibermom Avatar

    That’s what I always say, too.