Thursday, July 29, 2010

Conditionals, requests, language acquisition (i.e. more on Gracese)

So last night I was reading Grace a board book about birds. The board book actually pretty much is dedicated to defining "birds", which would make it an interesting subject for a post on word meanings some other time... the pages said things like "most birds fly" and "all birds have feathers." After reading to Grace about feathers and looking at the picture, I asked Grace...

me: would you like to have feathers, Grace?
Grace: (after a pause) Daddy, why did you say I can have feathers?

A couple of cool things here. 1. Grace used the verb "say" to indicate the presuppositional content of what I said (i.e. to mean "imply"). 2. Grace heard "would" in the polite sense whereas I meant it in the hypothetical sense -- polysemy exists in way more places than just word meanings.
In case it's unclear, let me spell out the intended and understood meanings of my sentence:
intended: imagine having feathers -- what would that be like?
understood: Have some feathers, if you please.

Grace's misunderstanding seems unlikely because I tend to think of the hypothetical meaning of the conditional as primary. Thinking about the history of language, this seems true -- the tense serves for talking about possible but not-yet-true realities, and has then been ritualized in polite forms in which we ask indirect questions rather than make requests of each other. But of course in the world of a toddler, indirect questions are much more common than hypothetical situations. My first thought on hearing Grace's response was that Grace may not understand the hypothetical meaning of the conditional at all -- she may know it only as the form we use for polite requests.

This is something I often see when we ask Grace to rephrase a demand in more polite language. Like most parents, we are merely expecting Grace to say "please." But often Grace rephrases without the please, but using the more polite indirect form.

Grace: Bring me milk Daddy, right now!
Me: Grace, can you ask for that more nicely?
Grace: Would you bring me milk right now daddy?
Me: Can you be a little more polite?
Grace: Would you bring me milk right now daddy pleeeeeeease?


Of course, the "would you" transformation is probably a more important bit of learning than the "please" bit. Now to figure out how I'll know when she's actually learned to use hypotheticals...

Sunday, May 30, 2010

iTunes sucks

I feel like in the GNOME world, it's often an unspoken assumption that Apple sets the standard for good design, and that the free software folks just hobble along trying to meet it.

Having not used Macs extensively since the quite-well-designed OS 8.6, I've often assumed this is true (nevermind the poor design of the "Dock" etc).

With K's lovely new iPhone, I had occasion to download iTunes lately (and I kept Windows on a partition of my new laptop just for this purpose -- ugh). This is a sort of submission, ever since my unfortunate altercation with a Mac Genius last time we bought a Mac product, when said genius knew virtually nothing of what file formats the iPod supported and could only tell me, repeatedly, "you just use iTunes."

Well, now that we have an iPhone, it appears you in fact have to use iTunes (things don't just work in Ubuntu with it, and you can't buy cool stuff for it without iTunes anyway), and all I can say is iTunes deeply, deeply suck.

Here are just a few experiences so far:

1. I try to copy a movie to the iPhone. I drag and drop it -- this is the paradigm of virtually every mac app everywhere since multifinder was introduced. This starts playing the movie. Nowhere can I figure out how to exit the movie -- I finally quit the program and reopen, at which time I have to reenter my password information.

2. I can see my shared library from my Rhythmbox machine -- sweet! But I can't copy the songs or download them to iTunes, even though they're DRM-free easily-copiable songs in the linux world (I only buy music from Amazon so as to avoid DRM).

3. I copy my music library into iTunes from a networked folder since the "magic" way didn't work and the app hangs. I have to force quit the application, leaving me with about 1/5 of my music library.

4. I try to "sync" the iPhone to the program in order to let Katharine update her Audobon app and install her newly downloaded TV show. I get a series of confusing messages about syncing "erasing" everything on the machine. Finally, I click "OK", rather frightened of Katharine's losing all the apps she's already paid for. Fingers crossede.

Long story short: the "syncing" model is rather confusing, iTunes is buggy and doesn't seem to be threaded properly so that one operation (importing a library) hangs up the program with no easy way to pause that operation. Furthermore, long operations such as syncing don't include time estimates.

Of course, on the plus side, the iPhone itself is pretty sweet. According to K anyway -- I don't really get to play with it much, and I don't dare to since I might want to write apps for it, which dooes not exactly promise to be a free and open experience to say the least.

I'm pretty sure any neutral comparison of iTunes to Rhythmbox would have Rhythmbox dominating iTunes in usability and feature set. Except, of course, the ability to work with the Apple store -- but that's not exactly Rhythmbox's fault.

Wednesday, May 5, 2010

poop, the past tense, and phonological features

So last night Grace said, "I pooped," a pretty typical sentence (we're mid potty training here). Here's how she said it:

ai pʰupʰɪt

This struck me as a pretty interesting utterance.

Background
Here's the relevant background information. First, the Standard English past tense here is formed by two simple rules.

1. Gramatical rule: Add "d" to create the past tense (unless the word already ends in "d/t" in which case you add "ɪd" in order to make the "d" audible).
2. Phonological rule: In a consonant cluster, the voicing spreads from the first consonant rightward in English (the opposite can happen at other times -- as it does in Spanish, for example, where voicing spreads leftward to affect the pronunciation of the "s" in "mismo" or "beisbol").

poop --> (grammar) poopd --> (phonology) poopt
One more piece of background information that is important is to understand Grace's rules for syllabification. Grace has for a long time not permitted consonant clusters. This is pretty typical of children's speech in English, and is typical of many languages throughout the world so it's also true of many accents. Her basic rule is that a syllable consists of C + V + C, where C is one consonant, V is one or more vowels and C is one consonant. When a word contains more than one consonant, Grace has two options: she can ignore a consonant or add a vowel. In practice, she does both, as in the following pronunciations:

Grace's syllabification at work
James: "dʒeimɪz" (standard pronunciation: dʒeimz)
Books: "bʊtʰɪz" (standard prononciation: bʊks)
Star: "tʰɑɹ" (standard pronunciation: stɑɹ)

These have been standard Gracese for a while. Obviously under the pressure of the Standard English she hears every day, all of these formations will eventually give way to the standard ones, and we have started to hear the occasional consonant cluster out of Grace already.

Analysis of Poop-it
Given Grace's rules for syllables, and Grace's frequent formation of past tense words in English with the "d" suffix, I would have expected her to form one of the following two forms:

1. Gracese: pʰupʰɪd (poop-id)
2. Standard: pʰupɾ (poopt)

What she did, however, is she formed a hybrid. This raises the possibility that she has learned neither the grammar nor the phonological rule described above, but has instead simply heard the word form "poopt" and interpreted it based on her own rules for syllabification.

This shouldn't seem that surprising, but to me it is. Listening to her talk, it seems so clear that she is using our grammatical endings "z" (plural, third person) and "d" (past tense) in a variety of contexts. But of course, it's entirely possible that instead of hearing Grace alternate between uninflected forms ("I poop") and inflected forms ("I poopit"), what I have in fact been hearing is simply her alternating between two pronunciations/interpretations of the to-her unpronouncable ("I poopt): "I poop" and "I poopit").

Of course the real proof that she is inflected verbs at all will only come when she begins to create novel (i.e. erroneous) forms like "goed" and "throwed." I can't say for sure whether I've heard these yet -- given how common they are in kid-speak and how interested I am, it's likely we haven't hit this phase yet.

Except that my second example of Grace's syllabification above is in fact a novel form: bʊkɪz. If Grace were in fact simply hearing and mimicking the word form, we would predict "bʊk" or "bʊkɪs". So are these novel forms? Has Grace learned to inflect for number but learned tense simply as "vocabulary"?

Hard to know for sure, but for the next few days I'll be paying close attention to those verbs and nouns that end in unvoiced consonants.

Sunday, April 25, 2010

Lanugage Explosion, Subordination, Intonation

Looking back over this blog, it's hard to believe that just two months ago I was still making lists of new words in Gracese. Now creating any such list would be an enormous and absurd undertaking -- new words show up daily, ranging from "preying mantis" and "mulberry bush" to "namaste" and "forsythia" and Grace is starting to know things I don't know (she taught me the words to "pop goes the weasel" last night, and she can list of the last names of all of her classmates -- most of which I can't interpret or reproduce accurately).

Grammar is still something I can try to track, though. I posted a while ago on subordinate phrases in Grace's language. Grace is beginning to use complementizers on occasion (where/how/for), but for the most part she still prefers the null complementizer (e.g. "I tell mommy Clara has a poopy diaper") and uses null complementizers even in cases where standard English does not allow it ("*I not know this goes").

Of course, with null complementizers, a skeptic might tell me that Grace is not in fact saying "I tell mommy Clara has a poopy diaper." but "I tell mommy. Clara has a poopy diaper."

To disprove the skeptic, I'd need to get out my recording equipment -- I'm quite sure that you can hear the punctuation difference quite clearly, not just in the lack of a pause but in the intonation ("Clara has a poopy diaper" sounds different in a subordinate phrase than it does as a standalone sentence -- said more quickly, with less stress, perhaps lower tone -- I don't really have the technical vocabulary to describe this correctly, but I'm quite sure you know it when you hear it).

All of this has me thinking about how I teach high school students to recognize subordinate phrases, a skill that comes in handy in at least three places: 1. Correctly punctuating the increasingly sophisticated sentences students try to write in high school. 2. Correctly reading complex sentences in writing by folks like Hawthorne, Dickens or Shakespeare 3. Understanding where the subjunctive is used in Spanish (as hinted by the "sub", the subjunctive can only occur in subordinate phrases).

I usually follow the "dependent/independent" clause method for describing subordination -- asking if a clause can stand on its own or not (if not, it's a dependent clause, a subordinate clause, and might have a subjunctive verb in it). Of course, there are cases where this fails, as in Grace's "I tell mommy Clara have a poopy diaper" where either clause could stand on its own. How then to explain to the student that "I tell momy" (Le digo a mamá) is the main clause and "Clara have a poopy diaper" (Clara tiene/tenga un pañal sucio) is the subordinate clause?

It strikes me that teaching them to recognize the intonation difference in the two clauses might be quicker than trying to teach a heuristic for determining which clause is dependent. It also would teach a valuable reading skill -- incorrectly reading a subordinate clause as a main clause is a major error in reading that leads to errors in comprehension. Yet I fear because we lack a clear language for describing it, this is an error that gets corrected much less reliably in teaching reading than less grave errors such as mispronouncing an unfamiliar word (the mispronounced word reveals a single gap in the puzzle; the misread subordinate clause shows the student has missed the very structure of the puzzle they're working on).

On the Spanish side, that leaves me only the exciting task of teaching them the difference between the very normal "Le digo a mamá que Clara tiene un pañal sucio" and the extremely odd "Le digo a mamá que Claro tenga un pañal sucio." which not only asks for a dirty diaper but implies that mom has the power to control Clara's bowl movements...

Monday, April 12, 2010

Thoughts on Lesson Planning

Like many teachers I know, I don't really write lesson plans.

Let me rephrase that, I have historically written plans for one of three reasons:

1. When someone was going to review a lesson with me (i.e. a supervisor would observe or a team would look at one as a model or to critique).
2. When co-planning (i.e. when another teacher was going to be using my plans the next day.
3. When required to (i.e. during my student teaching when I had to hand in all lesson plans).


When teaching on my own, writing individual lesson plans has never risen on my priority list above, say, working on something that students would be given, tweaking a project description, assessing student work, or working on longer-term planning.

That said I've certainly taught classes that would have been better if I'd taken even another 10-15 minutes to plan better. And of course I reinvent the wheel all the time, whereas if I had better plans I could theoretically be revising and revisiting rather than redoing and reinventing.

So the question this raises for me is how can I force myself to do those extra 10-15 minutes of labor to plan better and document what I'm doing for posterity without recreating the lesson plan templates of my student teaching that I find so overwhelming and droll.

Part of the problem, I believe, is that most of teaching I hold in my head. If I walk into class with a poem and three questions in my hand, I'm bringing much more: an idea about which vocabulary words will cause trouble and how I will pre-teach them in a drill, a sense of which lines are most difficult and how I will guide the whole class through an understanding of the difficult lines before setting them up with the (easier) rest of the poem for independent work. I also likely have a template to how my day goes -- we start with a drill, then have a Q/A with the whole class, then do small guided group or individual work followed by prolonged work and a wrap-up. If I take the time to explain it, there's a whole plan in there, but all I actually need are the questions and the poem, maybe with some underlining to indicate words to pre-teach.

Currently, many such templates mostly exist in my head, but I could probably benefit from writing them down. Templates would describe certain kinds of flow that could, over time, be refined, revised, and perfected. I could also come to notice those tasks for which I don't have a clear template and then start to chip away at the question of how best to teach them. For a given level and subject area, there may only be 5 or 6 templates over all: all classes fit those moulds. An individual lesson plan would then consist of basically a set of parameters that would slot into the template.

The list of parameters would likely take up no more than half a page, which is about the length of plans when I make them now (actually, now my usual length is a sticky). The beauty of something so short is that it is more readable and more adaptable for future years. Even when I have full lesson plans now, the very thought of reading a multi-page document is overwhelming. Having an ever-evolving description of a few templates in addition to sticky-length plans that reference those templates seems like something a more-effective version of me could actually do.

What's more, I have a feeling that both of these kinds of documents (templates and parameters) would be more useful to other teachers than full lesson plans. One frustration with trying to use other people's plans off the internet is that inevitably there are too many accidental factors that may or may not fit your class (class length, logistical rituals, etc.). Giving someone just the parameters -- here's the objective, the problem set, etc. -- would let them plug it into their own template for good teaching.

On the other hand, if what you're looking for is good instructional practices, then you want just the reverse -- a template that you can slot your own content into.

So this is my new idea. In programming, this is very common -- essentially I'm talking about separating data from display, or separating the model from the view. So the question that now occurs to me is: who else has had this idea? What names have they given it? Do there already exist books full of templates and parameters?

The other question of course is about the risk of abstraction. I am often guilty of the sin of over-abstraction in programming, and is it possible that templates, in the end, would be too leaky? I'm not sure, but I'm going to try to find out -- my goal for the end of this year is to start writing up templates and parameter sets. We'll see where it gets me.

Monday, March 22, 2010

Champion Teachers misteaching grammar

Inspired by the New York Times article a few weeks ago, I started reading Doug Lemov's Teach like a Champion in spite of a title so bad I can hardly bear to repeat it here. I very much like the idea of a teaching book that focuses on the mechanics of teaching, rather than on higher-order ideas that so often can become muddled or meaningless in practice.

Completely incidental to the points the text is making (which are content-neutral), I've already found two examples of "good" grammar teaching that are rather distressing to me.

In the first, the answer is right but the definition wrong, in the second, only the definition, which is wrong, is given.

1. Definition of a Subject

The task is to identify the subject and the sentence is: "My mother was not happy." The student (A) in the example guesses "happy." The teacher asks for clarification from another student (B) and gets the definition that "The subject is what the sentence is about." The teacher says this is correct and then asks student A what the subject is again. Student A replies "mother." End example.

This is an example of the rule "No opt out," where students always are forced to give the right answer, even if they at first get the answer wrong. You might think that the teacher above was just going easy on student B to move the lesson along, but the next section of the book, "Right is right," is about how important it is not to pretend students are right when they're not, so I think we can safely assume that Lemov thinks this answer is right.

If you're wondering why the definition is wrong, it's easiest to just give some counterxamples:
1. It is raining. Grammatical subject: "it." Subject according to above definition: rain.
2. "It is a truth universally acknowledged that a single man in possession of a good fortune must be in want of a wife." Grammatical subject: "it." Subject according to the above definition: marriage.


2. Definition of a Noun.

The task is simply to define a noun. Lemov gives the example of a student who says "A person, place or thing." The champion teacher does not accept this answer but prompts a more thorough response, until given "A person, place, thing or idea."

The importance of the idea clause here is telling, because it is the vagueness of the concept "idea" that has let so many educated people believe this definition for so long. It is, after all, entirely obvious that not all nouns are people, places or things. However,if you consider that things like "liberty," "truth," and "proof" are ideas, conceptual entities if you will, then it seems like this definition might just do.

The trouble is many nouns are clearly actions. In fact, we have suffixes that let you turn verbs into nouns, thus creating newly minted nouns out of any action we please. Here are a few very simple cases of nouns that are not people, places, things or ideas:

"Destruction" as in "The hurricane resulted in devastating, wide-spread destruction."
"Liberty" as in "I am not at liberty to say."


How would I define "noun," you may ask. I teach students the following simple procedure for identifying a noun. It is not perfect, but it is close, and it doesn't include any out and out lies: "If for a given word X you can say "the X" but not "very X", then X is a noun." Every native speaker can apply my rule perfectly every time.

Wednesday, March 17, 2010

Grace's first linguistic question...

Following up on the topic of taboos, Katharine reports that today Grace asked her her first question:

G: Mama, what's doo doo?
K: poop.