Tuesday, May 25, 2004

Grumbles and a BlogBirthday

Wow. So when I actually start trying to keep a regular posting schedule, it turns out I have a fair amount to say. Or at least maybe I’m just more aware of blogworthiness. In any event, as was the case last week, I’m totally swamped at work, but since I’ll be offline at least until Friday (and probably until Sunday or Monday) I wanted to make a few quick posts. This will be the administrivial one (which is easier to write). The more substantive ones. . . well, I'm tired of promising content and delivering meta, so it'll be up when it's up.

Grumble grumble grumble. Last week, I got linked from a site called TeamDandy. This produced a hit spike, which excited me and got me all happy. For like a minute, until I realized that I had a wet computer (don't ask) and a ton of work, and there wasn't going to be any substantive post forthcoming. So all those nice people went away.

Now, eventually I have to sit down and figure out what my relationship is going to be with the hit counter. I make a big deal of this being anonymous, except that anyone who reads it and knows me will glark [fn1] it in about five seconds. I make a big deal out of not publicizing this blog, except whenever I comment on the other blogs I visit, I make sure not only to link to it, but just to make sure Google gets what this blog is about (and stops confusing me with sites about David Frum), I GoogleWangle those comments with a tag like Orthodox Jewish Father. Clearly I'm conflicted.
[FN1:] I know that's not exactly how glark is used, but when I was looking up the link for a dictionary definition of grok (which I also realized wasn't what I meant) I followed links to the word and just really liked it.
But apparently my hits mean something to me, because when I realized that I had a traffic spike that I wasn't going to be able to follow-up with, I kept thinking, Wait! Come Back! There'll be good content soon! (Better link, with related sound file). When I come back from the holiday!!

Which brings me to my next point.

Which holiday? Why Shavuot, in fact! Look at my first post, ever!, footnote 6, for a reference to the very same holiday, just last year.

Which makes it almost exactly a year since I started this blog. A lunar year, anyway; I have a few days for the solar year to swing around. Though I'm not sure if I should count it, since I took that nine month break in the middle there. Happy Birthday to frumdad.blogspot.com!

I know my BlogRoll is a mess, and I know the site could use some template work. I'll do it, honest. Just not right now. Look at the time stamp of this post and realize that I'm still at work, and you can figure the stress I'm feeling to get! out! now!

So that's what I'm going to do.

To those to whom this is appropriate: Have a good holiday.

--FD

Labels: ,

Thursday, May 20, 2004

Trembling

I've posted that I was particularly busy at work this week, and I am. Tonight of all nights I'm going to be here late and I need to get this thing that I'm working on done.

But I'm having real trouble focusing.

Among the little notes I leave myself, "things to blog about!" there's one that points to the fact that becoming a father has made me a big sappy goofball, who gets emotionally moved by things that (a) wouldn't have done so before and more importantly (b) don't deserve to move me they're so patently maudlin.

I'll write that post, eventually. But right now I'm supposed to be concentrating on some point of legal arcana and I'm instead struggling not to just put my face in my hands and pray or cry or both.

News article here. I can't even bring myself to link it properly, because I would have to retype the headline and have it on my site and that would be too much for me right now.

I am refusing to believe that the father/suspect was particularly evil or stupid. Unless I learn otherwise (from a reliable source) I'm just going to assume an incredible horrendous accident, a problem with communication, something -- anything.

The family in question is clearly "frum," with the same meaning as the "frum" in FrumDad. That the family is frum doesn't make the situation any more of a tragedy -- and I wouldn't even think that if they weren't frum it would make it any less of a tragedy -- but it hits me a lot closer to home this way; it's a lot easier to see me in them -- in him.

HaMakom yenachem et'chem b'toch shar avay'lay Tzion vee'Yerushalayim

Maybe now I can get some work done. And then I'll go home and hug my child.

--FrumDad

Labels:

Monday, May 17, 2004

*Another* "Protect" follow-up

Yeah, I know; this is just lazy blogging.

The fact is this week is looking totally hairy at work and at home, if I do get to post it'll be short and probably Friday.

So when I saw this post, I thought it would make a nice follow-up to my Protect post, but more with the funny.

--FD

PS: The hairy picture is from this site, which I link only because I feel bad direct linking to the picture without linking to the site. I haven't even really looked at or read the site, and make no endorsement or promises or anything. I just did a Google Image search on "totally hairy."

Labels: , ,

Thursday, May 13, 2004

Irony 3a(1)

Remember the big controversy with Alanis Morissette's song, Ironic? (No link; it's a lame song.)

So at the end of the day there is a meaning of the word, "ironic," that could be read, if you squint, to apply to the situations in that song. Merriam-Webster Online's third definition -- thus the "3a(1)" in the title -- reads: "incongruity between the actual result of a sequence of events and the normal or expected result."

Well, this doesn't exactly qualify, but it's close.

In yesterday's post I wrote:
And then I wondered why I wasn't bothered by the possibility that she would (Ch'V) get hit by lightning, or that a tree limb might (Ch'V) fall and hurt her. Or why I wasn't worried about a tree falling on the house and hurting either Rachel or G. It's not that such things are impossible, or even entirely improbable.
Emphasis added. I wrote that about the storms on Tuesday night, and last night when I went home my lovely wife G informed me that in fact, a chunk of tree had fallen on our roof, above the baby's room, and we were now taking on water.

It's not a big deal, damage-wise, and no one was hurt. G, as I've mentioned, doesn't know about this blog and presumably doesn't read it. (Though, if she has been reading it and not realizing it was me, then this post will probably lock it down for her and I'll hear about it tonight. In which case, "Hi, sweetie! :)" )

But apparently God, with that great sense of humor of His, has an Atom feed.

--FD

Labels: , ,

Wednesday, May 12, 2004

The First Law of Fathering: Protect.

I don't know how long ago, Isaac Asimov laid out his Three Laws of Robotics. Basically, he posited a series of directives built into the essence of a robot that had primary control over any decision that robot made. So, the First Law is, "a robot may not injure a human being or, through inaction, allow a human being to come to harm." This law takes absolute priority and controls any other directive, intention, or action. The Second Law is explicitly designed to accommodate the First Law, ending with, "except where [following the Second Law] would conflict with the First Law," and the Third as well. Much of Asimov's fiction deals with situations that require a bending or breaking of the Laws, or that explore ambiguities in them.

Now, the meme has sometimes been picked up and sometimes been disregarded by science fiction writers and robotocists alike, and Asimov himself eventually came up with a "Zeroth" law to trump even the First law, but the underlying idea -- that if properly understood, right action in any situation can be addressed at least in some measure by a fairly limited set of directives -- is a good one, and an intriguing one.

This idea has an analog in Torah thought as well, though it's not entirely congruent. I can't find the sources for it as I write this, but take as a premise the idea that halacha is adequate to deal with any situation in life. There is a principle that almost all (if not all) halacha can be traced back to the 613 explicit commandments in the Torah, and there is a Talmudic source that discusses the slow recapitulation of the 613 into shorter and shorter lists, each of which contains in a kind of fractal origami the entirety of the others. I say it's not entirely congruent, because Torah law, like life itself, is more subtle, and (at least in my opinion) actually works to address any situation that could possibly arise, as opposed to the Asimov laws which are not and don't (and maybe that was part of the point of them.) There's a principle in medicine, "Primum non nocere," (First, do no harm), but if that were all there was to it then surgery -- which necessitates cutting open the patient -- would be off-limits. So it's really "First do no harm except when you should be doing harm because it comes out a net plus," which is much less pithy.

Which is all another way of asking the same question that drives much of this blog: What would be the essential, reductio-ad-necessitum Laws of Fathering? (And no, I don't think reductio-ad-necessitum is an actual phrase, but it does what I need it to.)

But I think I've got a handle on maybe the First Law of Fathering. Protect. Or, to paraphrase Asimov, "a robot father may not injure a human being his child or, through inaction, allow a human being his child to come to harm," which doesn't even really capture it half so well as, "Protect the child."

Now, I should admit, I'm going a little backwards here, in that I haven't so much derived this from first principles as I've reverse engineered it from the things I find myself thinking and feeling since I've become a father.

I remember quite clearly the intense surge of protectiveness that went through me when I first held Rachel. Through the tears, I remember whispering to her a promise that I was going to take care of her, that everything was going to be okay. And there wasn't even any crisis. G was fine, and the baby was fine and everyone was fine. But that was one of the first and most powerful understandings I came to; that it was now my job -- possibly my most important job -- to make sure that no one and nothing hurts this little girl.

I realize it's a little lot more complicated than that, more like the doctor's rule than the robotics rule, but the main thrust of it is very stark, and very pure. I know that learning to walk will mean that she will occasionally fall, just as I know that learning to love will mean that she will occasionally have her heart broken; but that's an intellectual imposition on my instinctive desire to pad the floor, or maim the boy. Even now, just writing about the moment, I am suffused with the same flush of that feeling. And surprised again at the sheer intensity of it, the heat of it.

I thought of this again in a few different situations over that past couple of weeks, variegated and not worth going into here, and then it sort of crystallized for me the other night.

G and I have been going back and forth about the whole vaccination thing since Rachel was little. I've read some baaaad stuff, and got a little freaked out when G came home with Rachel from the first pediatrician's appointment I had missed and informed me about Rachel getting this shot and that shot and so on.

G's a lot more white-bread than I am, so she pretty much thinks this whole brouhaha with the vaccines is just a little shy of silly panic-mongering. On the other I'm a borderline conspiracy wacko who is only really convinced that there isn't a hidden cure for cancer by the fact that there'd be so much money in making one happen.

So that debate's been coming up again occasionally, as Rachel has other appointments or as we find things that support our point of view. (Wanna be terrified? Read this article from Mother Jones. They want $1.50 to read it, but I thought it was worth it.) And at the end of the day, I can see G's points, and she can see mine, and we've come to a balance about things. (Certain vaccines can wait, ask the doctor about any mercury in the vaccines, etc, but Rachel does, generally get her shots.)

What I've been trying to parse out, though, is why I got, for instance, so angry reading the Mother Jones article. And then, a few nights ago, lying in bed listening to (and watching) the thunderstorm out the window, I had one of those meandering chains of thought that brought it into slightly better focus. (Better thunderstorm link.)

I was thinking about how, when she's a little older, I could imagine taking Rachel outside to play in the storm (something I am wont to do). How much fun it would be to run through the puddles and be startled by the flash and crack of the skies.

And then I wondered why I wasn't bothered by the possibility that she would (Ch'V) get hit by lightning, or that a tree limb might (Ch'V) fall and hurt her. Or why I wasn't worried about a tree falling on the house and hurting either Rachel or G. It's not that such things are impossible, or even entirely improbable.

(Ch'V = Chas VeShalom, which translates, roughly, as God Forbid.)

What I realized is that I wasn't worried about those things because I had done all that was in my power to protect Rachel from them. Or if not precisely all that was in my power -- I could, after all, have the house reinforced with steel beams, and I could never take her outside to play in the rain -- then something like that. Something like enough.

The rest. . . the rest is a matter of trust. The lightning, the tree, whatever. Those are issues for Hashem to manage. And Hashem, Him I trust. I'm not saying no one ever gets hit with lightning or what we call bad things never happen. That's a different discussion for a different forum.

What I'm saying is that I trust Hashem, and the magical thing about that trust is that it's sufficient to satisfy the First Law of Fathering. I hand over part of that job (protect) to someone[fn1] I know both can handle the job and will handle the job.
[fn1:] Someone is obviously a figure of speech. Anthropomorphizing God is pretty dangerous stuff, but it still sounds better than something.
And that's why I get so angry at the Mother Jones article. The gist of the article is that Significant Members of the Medical Establishment (SMoME) knew there was a problem (set aside the question of whether there is or is not a problem at all) and for selfish reasons buried that information. The fact is, because I'm not a medical expert, because I did not go to medical school and would have probably flunked if I did, I also repose trust in SMoME. I am charged with the First Law of Fathering, to Protect my child, and I hand over some of that job to the doctors, because I am working under the impression that they also can and will do the job. There's always a part of me that's aware that the capabilities of medical science are limited, and SMoME won't always be able to help. But to find out that they won't is infuriating.

Then, trying to figure out why it was so infuriating brought me back to the beginning of this journey, to figuring out the essential Laws of Fatherhood, or at least what feels like the First Law. But lying there, in my bed, G breathing softly beside me and Rachel in the next room (recently checked-in-on), I wasn't worried, or upset.

Because yes, the world is full of unknowns, full of potential harm to my child; it is, essentially, bigger than me. But it's also so beautiful, and designed and managed by one of very few entities who I trust, implicitly, to watch out for Rachel as much as I watch out for her.

And that was how I finally let myself fall asleep.

--FD

Labels: ,

Tuesday, May 04, 2004

Fatherhood is Leaving Over the Extra-Nummy Bits.

My wife makes this sauteed asparagus with garlic that, though simple, is truly extraordinary. (Enough so that even though this isn't exactly "recipe corner" I'll throw in a footnote at the end with the basics of how it's made.) While I do a fair amount of cooking around the house, Sabbath preparations are given over entirely to the lovely and talented G, who (knowing my penchant for them) often cooks up a batch of these for the table. She makes enough that there's usually a tuperware-full or so of leftovers.

Every bit my daughter, we discovered last week that Rachel really likes asparagus, too. We cut them up a little bigger than bite-size, and a handful on the table of her high chair will keep her busy for a while, and as importantly well fed. She likes them so much that she actually cried when we took the container away from the table, since she had figured it out and was (successfully) reaching for it. We like to feed her the tips rather than the stalks, because (a) she likes them better (probably because they're a little sweeter and less cellulose-y than the stalks) and (b) because they're easier for her to chew, getting more stringy the further away from the tip end. I'll add in that I like to feed her the tips because I like the tips, too, for the same reasons (a) and (b).

Last Saturday night, as happens fairly often on Saturday night, I was feeling like a little rumbly in my tumbly and went to the fridge and grabbed the container full of asparagus, and headed downstairs to our guest room/office to get some work done on some project or another.

Referring to a time about a month ago when, in a similar situation, I had eaten all of something that G had been saving for herself, I joked, "don't worry honey, I won't finish it all this time." G, no slouch she, shot back with, "I know you won’t, Rachel likes those."

Which I'll admit I didn't one hundred percent hear until I got downstairs. But then, as I'm plowing into my first forkful, I thought of it again.

And twenty minutes later, I'm still a little peckish . . . and I'm looking at a tupperware-full of tip ends.

Object lesson: Fatherhood is leaving over the nummy bits.

--FD

Recipe bonus: I know you want to know how to make the asparagus in question. G says the trick is to soak the asparagus in cold tap water for about 5 or 10 minutes, with a generous amount of kosher salt, then pour that off, drain a bit, and sautee in an open pan until almost done, then cover the pan for a bit. Turn off the heat, but leave the cover on and in another 5 minutes you got asparagus. Okay, it's not Iron Chef, but believe you me it's mightee tastee!

Labels: