7 September 2007 to 29 April 2007
1. Good light.
2. Elevate child to proper height.
3. Remove awkward outer casing from instrument.
2. Elevate child to proper height.
3. Remove awkward outer casing from instrument.
It should be possible to refer explicitly to something particular on a web page. To anything, whether or not the page's author thought to assign it a (secret) labeled ahead of time.
The most obvious way to mostly provide this, it seems to me, is for the HTTP URL syntax to include a way to specify a search string at the end, which the browser simply plugs into its own Find function after loading the page. I will randomly suggest that since we already have "#" for fragments at the end of a URL, and valid fragment IDs must begin with an alphanumeric or an underscore, "#=" could be used for passing search text. So where
http://www.furia.com/page.cgi?type=log&id=273
refers to this blog-entry as a whole page, you could also do
http://www.furia.com/page.cgi?type=log&id=273#=this+phrase
to refer directly to this phrase.
For extra credit we could also support "@" and a number for getting to the Nth use of that text. So
http://www.furia.com/page.cgi?type=log&id=273#=this+phrase@2
would refer directly to this phrase, not the one above.
Useful, semantically reasonable, eminently implementable.
[See the discussion on vF.]
The most obvious way to mostly provide this, it seems to me, is for the HTTP URL syntax to include a way to specify a search string at the end, which the browser simply plugs into its own Find function after loading the page. I will randomly suggest that since we already have "#" for fragments at the end of a URL, and valid fragment IDs must begin with an alphanumeric or an underscore, "#=" could be used for passing search text. So where
http://www.furia.com/page.cgi?type=log&id=273
refers to this blog-entry as a whole page, you could also do
http://www.furia.com/page.cgi?type=log&id=273#=this+phrase
to refer directly to this phrase.
For extra credit we could also support "@" and a number for getting to the Nth use of that text. So
http://www.furia.com/page.cgi?type=log&id=273#=this+phrase@2
would refer directly to this phrase, not the one above.
Useful, semantically reasonable, eminently implementable.
[See the discussion on vF.]
¶ Death to False (Metal) · 8 August 2007 essay/tech
Two of the very bad features of the SQL-based conception of relational data-modeling, I think, are these:
- one-to-many relationships are significantly harder to handle than one-to-one relationships (and, inversely, many-to-one relationships easiest to handle by defactoring)
- absence is significantly harder to handle than presence
It's easy to add an Artist column to an Album table, for example, so we get:
But if you want to model the fact that collaboration albums can have multiple artists, you need an Albums table, an Artists table, a join table, and a bunch of IDs:
This is already a pain in the ass, and thus you get a world filled with cop-outs like this:
and this:
both of which are tolerable enough to just look at, but awful when you go to try to get the computer to answer even perfectly sensible questions like what albums Boris has done.
And then, when you want to add a little more detail, you really ought to do this:
but instead you'll probably try to get away with:
or
because if you have the latter, you can do:
which is easy to understand, although it won't work because you forgot you don't have a field called plain "Artist" anymore. Whereas with the five-table form you have to do something like:
and that's probably still wrong.
I submit that this is all a colossal mess, and it's a wonder the database-driven software we get driven out of it isn't even more woeful than it is. A better paradigm would embrace the opposites of these two flaws:
- the modeling of a relationship should be the same whether the relationship is one-to-one, one-to-many, many-to-one or many-to-many, and should be the same no matter how many "many"s you have
- absence and presence should be equally easy to assess
And I think a useful rough metric for such a new system is that it allows you to model your data without ever needing to say FALSE.
And I think this, I think, because I think this is how we think and talk about relationships between things when nobody is getting in our way:
Black One was recorded by Sunn O))), and was released in CD, LP and Download formats. Altar was recorded by Sunn O))) and Boris, and was released in CD and LP formats. All of these albums were released on CD and LP. Altar is the only one that wasn't released in Download format.
Take these out of sentence form and make the data-types explicit and everything is still perfectly straightforward:
or, looking at the same data from a different perspective:
and then the old questions are also easier:
Subliminating the one/many distinction allows us to talk about albums with 3 or 8 or 0 artists just as readily as we talk about albums with 1 or 2. Fixing the query language to handle absence lets us cope with the introduction of a new edition into our dataset, say, without having to add a new field for it and/or go through asserting that everything we already knew about doesn't have that format. I suspect pretty much every database field headed X and filled with TRUEs and FALSEs could at least be more usefully modeled in my new world as a relationship called "Characteristics" that either does or doesn't include X. And usually, as with formats, there's actually a meaningful label that contains information itself. The point is that things have relationships to their characteristics, or their formats. They don't, except in a very existential sense, have a relationship to falseness. FALSE is a machine thing.
The relationally astute will note that the five-table version is the fully-normalized representation that would support an SQL-based implementation of my new form as a display abstraction, and presumably my pseudo-query-code could be preprocessed into the messy SQL so I'd never see it. But that's my point: SQL is too low an abstraction, which makes it too hard to do things naturally, which makes it too hard to pass along natural behavior to the victims of the system. I'm mainly arguing for a better abstraction. (Although I also expect it's still always going to be bad that there's no better underlying way to represent lists, so I'm also probably arguing for the better abstraction to not merely be layered on top of the bad one.)
The discographically astute will note that Altar is available on iTunes, and that I have vastly undermodeled the rich and complicated space of Sunn O))) release formats. But if I'd done the examples in real detail, I'd still be typing out the bad versions...
- one-to-many relationships are significantly harder to handle than one-to-one relationships (and, inversely, many-to-one relationships easiest to handle by defactoring)
- absence is significantly harder to handle than presence
It's easy to add an Artist column to an Album table, for example, so we get:
| Album | Artist |
| Black One | Sunn O))) |
But if you want to model the fact that collaboration albums can have multiple artists, you need an Albums table, an Artists table, a join table, and a bunch of IDs:
Albums
| Artists
| Authorship
|
This is already a pain in the ass, and thus you get a world filled with cop-outs like this:
| Album | Artist |
| Black One | Sunn O))) |
| Altar | Sunn O))) / Boris |
and this:
| Album | Artist 1 | Artist 2 | Artist 3 |
| Black One | Sunn O))) | FALSE | FALSE |
| Altar | Sunn O))) | Boris | FALSE |
both of which are tolerable enough to just look at, but awful when you go to try to get the computer to answer even perfectly sensible questions like what albums Boris has done.
And then, when you want to add a little more detail, you really ought to do this:
Albums
| Artists
| Formats
| Authorship
| Formatship
|
but instead you'll probably try to get away with:
| Album | Artist | FormatCode |
| Black One | Sunn O))) | CD/LP/D |
| Altar | Sunn O))) & Boris | CD/LP |
or
| Album | Artist 1 | Artist 2 | Artist 3 | CD | LP | D |
| Black One | Sunn O))) | FALSE | FALSE | TRUE | TRUE | TRUE |
| Altar | Sunn O))) | Boris | FALSE | TRUE | TRUE | FALSE |
because if you have the latter, you can do:
SELECT Album, Artist
FROM Albums
WHERE D=FALSE
which is easy to understand, although it won't work because you forgot you don't have a field called plain "Artist" anymore. Whereas with the five-table form you have to do something like:
SELECT Albums.Album, Artists.Artist
FROM Albums, Artists, Authorship
WHERE Albums.ID=Authorship.AlbumID
AND Artists.ID=Authorship.ArtistID
AND NOT EXISTS (
SELECT *
FROM Formats, Formatship
WHERE Albums.ID=Formatship.AlbumID
AND Formats.ID=Formatship.FormatID
AND Formats.Format='Download'
)
and that's probably still wrong.
I submit that this is all a colossal mess, and it's a wonder the database-driven software we get driven out of it isn't even more woeful than it is. A better paradigm would embrace the opposites of these two flaws:
- the modeling of a relationship should be the same whether the relationship is one-to-one, one-to-many, many-to-one or many-to-many, and should be the same no matter how many "many"s you have
- absence and presence should be equally easy to assess
And I think a useful rough metric for such a new system is that it allows you to model your data without ever needing to say FALSE.
And I think this, I think, because I think this is how we think and talk about relationships between things when nobody is getting in our way:
Black One was recorded by Sunn O))), and was released in CD, LP and Download formats. Altar was recorded by Sunn O))) and Boris, and was released in CD and LP formats. All of these albums were released on CD and LP. Altar is the only one that wasn't released in Download format.
Take these out of sentence form and make the data-types explicit and everything is still perfectly straightforward:
Album: [Black One]
Artists: [Sunn O)))]
Formats: [CD] [LP] [Download]
Album: [Altar]
Artists: [Sunn O)))] [Boris]
Formats: [CD] [LP]
or, looking at the same data from a different perspective:
Format: [CD]
Albums: [Black One] [Altar]
Format: [LP]
Albums: [Black One] [Altar]
Format: [Download]
Albums: [Black One]
and then the old questions are also easier:
FIND Formats WHOSE Albums INCLUDE 'Black One' and 'Altar'
FIND Albums WHOSE Formats DON'T INCLUDE 'Download'
Subliminating the one/many distinction allows us to talk about albums with 3 or 8 or 0 artists just as readily as we talk about albums with 1 or 2. Fixing the query language to handle absence lets us cope with the introduction of a new edition into our dataset, say, without having to add a new field for it and/or go through asserting that everything we already knew about doesn't have that format. I suspect pretty much every database field headed X and filled with TRUEs and FALSEs could at least be more usefully modeled in my new world as a relationship called "Characteristics" that either does or doesn't include X. And usually, as with formats, there's actually a meaningful label that contains information itself. The point is that things have relationships to their characteristics, or their formats. They don't, except in a very existential sense, have a relationship to falseness. FALSE is a machine thing.
The relationally astute will note that the five-table version is the fully-normalized representation that would support an SQL-based implementation of my new form as a display abstraction, and presumably my pseudo-query-code could be preprocessed into the messy SQL so I'd never see it. But that's my point: SQL is too low an abstraction, which makes it too hard to do things naturally, which makes it too hard to pass along natural behavior to the victims of the system. I'm mainly arguing for a better abstraction. (Although I also expect it's still always going to be bad that there's no better underlying way to represent lists, so I'm also probably arguing for the better abstraction to not merely be layered on top of the bad one.)
The discographically astute will note that Altar is available on iTunes, and that I have vastly undermodeled the rich and complicated space of Sunn O))) release formats. But if I'd done the examples in real detail, I'd still be typing out the bad versions...
¶ 1 July 2007 child/photo
What Muybridge did for horses galloping, I will become famous by doing for tiny children sneezing.
¶ first loves · 23 June 2007 child/photo
My parents report, and I vaguely remember this myself, that for the first few years of my being allowed to go to movie theaters and see real (i.e., non-"family") movies, I would invariably come home after each one and deliver some epic panegyric insisting that whatever it was was the best movie I had ever seen. The only specific movies I recall thinking this of as an impressionable early movie-goer are The Eagle Has Landed, Capricorn One and Clash of the Titans, and I submit that it is not unreasonable to consider this an ascending order of quality, albeit in the last case maybe only if one was a 14-year-old boy in 1981 and hadn't seen pointedly naked movie-breasts in anything else yet.
You will eventually get to the age where we begin worrying about how to stage your exposure to adult concepts, too, and before that the age where we start having to negotiate with your own loopily underinformed idea of your personal tastes. But for now your comprehension is blissfully abstract, and pretty much anything is likely to be the greatest thing ever, or close enough for us to amuse ourselves by inferring the nuances of your reactions from the gradually-less-random expressions that flicker across your face.
I have been taking advantage of this state by attempting to give you a sweepingly unguarded pre-self-consciousness grounding in modern rock music. I realize this might sound suspiciously like me just listening to music while I'm holding you, but your reactions are both surprisingly organized and not what I claimed I thought they were going to be, so I feel like the experiments are at least marginally non-solipsistic. Later, no doubt, you will turn out to mostly like some new kind of music B and I fundamentally fail to grasp, but at least you'll have the benefit of some Manic Street Preachers b-sides buried deep in your psyche.
One of my favorite dopey anticipatory theories, developed a while ago after reading an evocative article about the sonic harshness of the womb, was that babies are naturally intuitive fans of deeply textural black metal. The coursing blood all around you, the sudden tumbling motions, the frantic gnashing hum of your own brain growing. Might as well call it birth metal.
This idea proves to have some limited sense to it, at least, in that churning noise at high volume has some undeniable visceral effect. There's a long stretch of the middle of Part II of Metal Machine Music that puts you to sleep approximately as effectively as the "ocean" loop on the sound-module that came with your pack-and-play. Likewise a few carefully-selected sections of Aube's Aqua Syndrome. The ocean noises also kind of work on Bethany, though, whereas Reed and Aube kind of make her want to encase her head in cement, so given the open format of our house, and our affection for her head, the ocean sounds usually seem like the better option in practice.
Little Tiggers do not turn out to like death metal at all, to my mild surprise and pro-forma-ly brooding disappointment. Even the Leviathan and Xasthur pieces I holistically experience as most textural prove to have far too many dynamic and tonal shifts at the second-by-second scale, and you're perpetually either getting restless during a quiet part or being startled when the noise blasts in again. Sad. Statistically this was the most likely age at which you'd appreciate death metal, in that there's not even the outside danger of your accidentally figuring out any of the words. Later you'll realize it's another silly thing that only boys like, and thus yet another thing for which I might as well apologize in advance.
What you like best, by far, is steady, propulsive, fast, opportunistically rock-inflected pop songs. Four minutes at most, three is better. No long intros or outros. Female singers more than men (but James Bradfield and Paul Smith are OK), and big bonus points for any break where everything drops out except the drums and vocals. B thinks this is all about how I dance with you during those kinds of songs, but you and I know it's more than that. Fefe Dobson's "Rock It Till You Drop It" is, after all, a very fine song about perseverance, or maybe equanimity, and I'm only dancing the way anybody should feel inspired to. The Go-Go's are cultural icons, and give us a way to understand how the Spice Girls embody the dangerous nominality of post-ironic identity. Shakira represents both the emotional vitality of culture and the insistent triumph over it of individuality and hair. Tommy heavenly6 is, I agree, universally charming, and by the time you're old enough to wonder what she's singing, maybe I'll again have enough spare time to translate it.
But in case you're ever really curious, your favorite song for your first two months has been, unquestionably, "U & Ur Hand" by Pink. I don't remember how I discovered this. You like "Who Knew" and "Leave Me Alone (I'm Lonely)" fairly well, too, but "U & Ur Hand" is clearly special. We have a special dance we've invented for it, you and I, and it has never, ever failed to please you. Once you went from beet-red squalling to fast asleep before it even got to the two-minute mark, but usually you just dance with me. Or, anyway, I dance, and you lie in my arms with your head nestled into my left armpit, gazing up at me with love. Or past me towards the nearest skylight, or lamp, or faint diagonal shadow, but I collect the love en passant.
As you'll appreciate when you're considerably older, "U & Ur Hand" is not exactly intended for children. I usually sing along, anyway. It's a song of aggressive feminine self-affirmation, mostly, so even if its specific defiance and injunctions aren't really age-appropriate for you, or gender-appropriate for me, I think it's healthy for you to be exposed to its energy.
And if B is right, and it's really only me you're responding to, then you're learning about how my goofy tastes in music and defiance become manifest in my body's movements and my heart's resonances, and although I don't need you to love exactly what I love, I want desperately for you to love what you love at least as jubilantly as I love what I love.
I've long since seen a lot of movies I liked more than Capricorn One, but more than a few I liked less. "U & Ur Hand" probably won't always be your favorite song, and it'll probably save your mom and me some tense parent-teacher conferences along the way if it isn't. But not everything always has to change, and your first intuitions aren't necessarily wrong. I'll play this for you again someday, when you've forgotten, and we'll see what we think. And, maybe, remember what this felt like, when every next minute with you was so amazingly likely to be the best one yet.
¶ These Pictures Can't Haunt You · 6 June 2007 child/photo
B asked me whether, now that I see how much work you are, I'm more appreciative of what my own parents did for me. I definitely understand what they went through more than I ever did before having you, but appreciative isn't exactly right, for either what I feel for my parents or what I expect you to eventually feel for us. I don't remember or identify with myself as an infant. This baby we're bathing in the sink, because it's funny to try once even though you're basically already too big, is not really you. Not yet. So these pictures can't haunt you. This stuff we're doing for you can't exactly be for you. You didn't ask for it, you can't be consulted for your informed consent, and you'll have to live with the countless mistakes we're undoubtably already making. Asking you to be grateful for all this, in any meaningful sense, seems to me to be tantamount to imposing original sin. At most, maybe, one day you'll do this for somebody else who won't really exist yet. But only if you choose to for your own reasons, not because you owe anybody any kind of debt. You do not owe us your life, we are merely holding it for you in trust. Having you makes me more aware than ever that gratitude for one's own birth is a footstep into an emotional minefield. We, your parents, must be able to unequivocally forgive you for whatever it takes to get you to the point where you become you, for everything you require before you are able to take responsibility for your own commitments and responses. Until then, this work we do cannot and must not be measured in any kind of currency, it must be a gift given freely to the world.
I'm afraid to post more pictures. I fear we may have unwittingly unleashed more cuteness than the world can endure.
¶ Watching you wake · 18 May 2007 child/photo
Mostly you sleep. "Mostly" in a statistical sense, at least, although somehow we are mostly not sleeping, so there's something subtly wrong with that term. When you aren't sleeping you are usually eating, or at least circling curiously around the possibility of eating. You have quickly settled on a terse, vigorous vocabulary of two exclamations: "Eh-eh-eh-eh-eh-eh-eh" means that you are hungry; "LLLLA!" means that you are uncomfortable. We are hoping you decide to specialize this latter complaint a little further before too long, because at the moment it is used whether the discomfort is amenable to external correction or not, which leads to your father churning through diapers at an ecologically alarming rate.
You're sleeping right now, and we're listening to songs we like because the only Mozart we have is violin concertos, and for B's sake we try to avoid pairing violins and sleep deprivation. They aren't sure about those Mozart studies, anyway. Basically, we discover the more we read, "they" aren't really sure about much of anything. So I guess we're mostly going to improvise. B is reading up on Montessori schools, even though she should be sleeping or showering or eating. I am taking nearly forever to write this short, bleary blog entry when I should be sleeping or showering or making us some lunch. It's hard to imagine paying somebody $17k to facilitate your self-directed growth, given that you haven't quite figured out how to self-directedly not smack yourself in the eye while you're trying to eat and poop at the same time. It's hard to say much about the process without violating the rule against describing the consistency of individual poops to anybody who hasn't explicitly enquired.
I think we are probably going to survive these first few weeks. I might not have said this so confidently six hours ago, but six hours ago I was too incoherent to say much of anything, so that's just a guess. Since then B and I have both slept about an hour. B has fed you twice. I've changed five diapers and washed my hands fourteen times and made breakfast and started some laundry and forgotten about the laundry and washed up from breakfast and looked up the causes of post-cesarian abdominal pain and taken B's temperature and checked the real-estate listings for a bigger house and made cryptic notations on my chart of your inputs and outputs and chased the cats around a little and cleaned up the glass one of them knocked off the table where I forgot it and made a grocery list whose contents and then location I have also subsequently forgotten. So you see that B has the far harder role.
In some ways, bringing you along into the world is easier than I expected. I had somehow not grasped that you would be so specific, right from the outset. I didn't want to say anything before, but in the ultrasounds you always looked a little generalized. Taking care of an infant abstraction sounded really stressful and difficult. Taking care of an incapacitatingly adorable miniature human is exhausting and mind-emptying, but basically simple. Doing so without sleep, of course, is still really stressful and difficult, but on this little sleep even counting to 24 by 4s is really stressful and difficult. Later, when you learn to count, this will mean something to you.
In the meantime, we are mostly just watching you learn to exist. "LLLLA!", you object. True enough. But it's worth it. You'll see.
¶ The first of a million hellos · 2 May 2007 child/photo
My daughter Lyra was born last night, 1 May 2007, at 8:33pm. She weighed 9 lbs 2 oz at birth, and 4140 grams after instinctively going metric as her first official act. Her birthday is exactly 27 days after mine and 27 days before B's, and 27 is three to the third, and she is the third of the three of us, so you see that her well-being is numerologically preordained.
I have changed the first (two) of a million diapers (and have not quite yet lost count).
We are no longer waiting.
You're not formally due until Thursday, so you're biologically entitled to spend a little while more inside, but we're ready to meet you, so, you know, don't feel obliged to stick it out just to make the number.
Meanwhile, people keep giving us "helpful" advice on how to lure you into the world. "Chinese food", they say. You're probably not old enough to understand why that's funny, given that you're not old in a technical sense. And yet, almost old enough to suspect that a billion Chinese people probably aren't all giving birth at 32 weeks.
Presumably they don't all methodically eat fortune cookies after each routine meal, either, although I admit that I haven't personally verified this. (Nor that they do not, in fact, eat fortune donuts after hamburgers.) (As you'll find out, people have ways of small-mindedly oversimplifying culture, and then of expansively and imaginatively recomplicating it.) (We'll go investigate once you're, you know, eating food without using your navel.)
Anyway, we got three fortune cookes with our last order. Mine said something about happiness. And fish, I think, or maybe the moon. B's dealt, somewhat evasively, with the subject of change. But yours I quote here verbatim: "If you wish good advice, consult your mother."
Meanwhile, people keep giving us "helpful" advice on how to lure you into the world. "Chinese food", they say. You're probably not old enough to understand why that's funny, given that you're not old in a technical sense. And yet, almost old enough to suspect that a billion Chinese people probably aren't all giving birth at 32 weeks.
Presumably they don't all methodically eat fortune cookies after each routine meal, either, although I admit that I haven't personally verified this. (Nor that they do not, in fact, eat fortune donuts after hamburgers.) (As you'll find out, people have ways of small-mindedly oversimplifying culture, and then of expansively and imaginatively recomplicating it.) (We'll go investigate once you're, you know, eating food without using your navel.)
Anyway, we got three fortune cookes with our last order. Mine said something about happiness. And fish, I think, or maybe the moon. B's dealt, somewhat evasively, with the subject of change. But yours I quote here verbatim: "If you wish good advice, consult your mother."