![]() |
![]() |
![]() |
![]() |
![]() |
Rabbi Shimon said: be careful with the recitation of the sh'ma and the t'filah (the main prayer). When you pray do not make it a set task but an appeal for mercy and an entreaty before the All-Present. R. Eleazar said: be eager to study torah and know before Whom one toils. R. Tarfon said: the day is short and the work is much, and the workers are indolent, but the reward is great and the Master of the house is insistent. (Avot 2:18-20, excerpted)
With the fixed text of the t'filah in the prayerbook being somewhat long, it can be hard to remember that the text was not always so fixed and to follow Rabbi Shimon's advice.
On the Mark:
So it's like this. I enjoy making music, both singing and playing, and while the SCA was providing opportunities to do that, it couldn't scratch the folk-music part of that itch. Filksings at SF cons, while also enjoyable, couldn't scratch much of the itch either; I don't play guitar and I don't write my own songs, so I felt like my offerings there amounted to "reasonably-well-done a-capella songs we've all heard before". But there was this group playing at cons called Clam Chowder that was doing the kinds of music I wanted to do -- rich arrangements, a variety of instruments, a mix of folk songs and filk and "found filk" and the occasional oddball piece. And I wondered if there was room for more of that kind of thing in fandom and perhaps occasional coffeehouses and stuff, so I asked three musical SCA friends if this sounded interesting to them, and it did, and off we went. (Because we were all in the SCA, we could easily incorporate the renaissance music we were already doing there into other performances -- bonus!)
Now this all worked pretty well when we were in our 20s and didn't have such demanding jobs and I wasn't yet paying attention to Shabbat and the only group members who were married were married to each other. We had a lot of fun for about 15 years and then shut it down on a high note. We didn't want to be one of those groups that slowly degrades while its friends sigh and hope you'll put it out of their misery, y'know?
I still listen to our CDs (well, mp3s now) sometimes and, well, gosh, we were pretty good. In my biased opinion. :-) I wish we'd done more music that we'd be free and clear to post online; I'd like to be able to share.
LISP
The most valuable part of my education as a technical writer was my student internship with the Common LISP project. It was also either the first- or second-most important part of my education as a software developer. Yes yes, the classroom stuff was important and the software-engineering project course was essential for putting the pieces together, but this was the real world and the real world is far less tidy than the classroom.
I was brought on to help write the documentation for this
then-in-development language. (Other varieties of LISP existed; this
was an attempt to unify them.) But unlike all previous tech-writing
work, this was for a thing that did not fully exist yet, and I was part
of the ongoing design process. I was there in the (virtual) room with
the lead designers, Guy Steele, Dave Moon and dozens of others big and
small, and if my contributions had merit it didn't matter that I was an
undergraduate with no real experience. On the ARPAnet nobody knows
you're a dog undergrad. Mind, being an undergraduate
with no real experience, I didn't necessarily have a lot of design ideas
to contribute, but even then I was pretty good at catching
inconsistencies and asking key questions. I learned to write
software-interface documentation there, but even more importantly I
learned to be part of a real software-development process, to ask
questions even if they might seem "stupid", to argue for technical
positions and support those arguments, and to be a full member of a
team.
When I graduated and met more of the real world I would learn that it usually doesn't work like this. In a lot of places, tech writers are not part of the development process (and may not even be in the development department) and the attitude is that they can come in after the big boys are done developing the product. Phooey on that; this important early experience taught me that it doesn't have to be that way, and I have held firm on this in every place I've ever worked. If I hadn't had this early lesson, I might well have fled the field.
It is also because of the Common LISP project that I went into programmer documentation (and expanded from there). Frankly, writing application documentation bores the heck out of me most of the time, but building software development kits is exciting and nourishes my inner geek. When I went to college I hadn't even heard of technical writing (I went there to do computer science), but I came out as a technically-proficient writer who knows the good that is possible. I have Common LISP to thank for that.
Comment to this post and I will pick seven things I would like you to talk about. They might make sense or be totally random. Then post that list, with your commentary, to your journal. Other people can get lists from you, and the meme merrily perpetuates itself.
He gave me: Lisp, On the Mark, Accessibility, Books, Role-Playing Games, Filk, Faroe Islands (one of these things is not like the others).
( Read more... )
So this week I offer a teaching from Pirkei Avot, which we read during the omer, the period from Pesach to Shavuot. Next week I expect to get back to the regular routine. This is one of my favorites:
Ben Zoma said: who is wise? He who learns from every person, as it is said: "from all who taught me have I gained understanding". Who is mighty? He who subdues his evil inclination, as it is said: "he that is slow to anger is better than the mighty, and he that rules his spirit than he that takes a city". Who is rich? He who rejoices in his lot, as it is said: "when you eat of the labor of your hands happy shall you be". Who is honored? He who honors his fellow, as it is said: "for them that honor me I will honor". (Avot 4:1)
The Rue plot in the book was very powerful, and I was disappointed that it was so highly abbreviated in the movie. I understand that a movie can't contain everything in the book and still be a civilized length, and they did a good job of trimming in general, but this one stood out as a misfire.
The book is written in the first person (first-person present tense, mostly, which is unconventional). This means that in the book you only see and know what the narrator knows. In the movie they showed some of what was going on "backstage" and I found those parts to be well-done, laying the groundwork for the political issues to come. They added rather than detracting -- not at all a safe bet when screenwriters decide to innovate.
Because of the POV, in the book the game-makers are largely invisible -- we see their work but don't see them. In the movie I thought the lead game-maker was particularly strong; seeing how what was going on in the arena affected him added a level of story not possible in the book. And oh, his final scene... nice touch.
A nit: I do wonder how Katniss was able to stay at full draw for so long, with a bow strong enough to kill a person, in that scene at the end. Especially given her state at that time. Just sayin'. (Also, what are the aerodynamic properties of silver arrows? The book referred to them as silver too, and it struck me as peculiar there too.)
The trailers I remember were:
Someone asked me this morning if any coins have been found in the Dead Sea. I have no idea. I wonder whether, at least for gold, anything would be left after all that time and considering the properties of that sea.
Edit: I just asked a related question about how this was managed over on Mi Yodeya (aka Jewish Life and Learning).
When nobody feels pressure (got to get upstairs to the bar mitzvah, got to beat the lunch guests home, whatever), we can relax and just take our time with services. I don't get that very often and I treasure it. We had kabbalat shabbat out on the porch in the fading sun (plus there were porch lights). Saturday morning after the service we had an energetic discussion of part of the parsha (Tazria [1]), interrupted only by our need to walk up to the main building for lunch (but it continued later in smaller pockets).
Speaking of which: ( Read more... )
Friday night we had a study session around the second chapter of Pirke Avot (teachings of the fathers, where a lot of the sayings we "all know" come from). We broke into pairs or trios to study for a while and then each group shared something it learned. We've used this study method before and I find it works well; it's harder to do in-depth study with 42 people all together, but by doing it this way I learned things both from my group and the larger group.
Saturday afternoon we tried something new. My rabbi asked a few of us to prepare chugim, short sessions to run concurrently, so people could learn what they want. I taught (well, lead a study of) a section of talmud -- how various rabbis concluded their individual prayer at the end of the t'filah. (B'rachot 16b-17a, for anyone following along at home.) I approached this from the prayer context, not the talmud context -- we have this fixed text that we say every service and then we're supposed to say our own prayer, but maybe not everybody is comfortable doing that. The idea was to present a range of things that are recorded in our tradition; maybe people would get some new ideas.
I had not realized, and did not think to ask at the beginning, that no one there other than me had actually studied any talmud before -- maybe they'd seen material that came from the talmud, but they'd never looked at a page of talmud before. I, not knowing this, gave only the scantest of introductions to talmud itself (here's what the full page looks like, here's where we are, here's an interlinear translation to follow 'cause nobody here including me is going to read the Aramaic straight from the page). When I learned at the end that this was new to everybody, part of me wondered if I should have given more of an intro -- but I think not, on reflection. I helped a group of people just dive in to something that many consider intimidating; I think that probably left them all feeling better, and more confident, than a "talmud 101 using this text as an example" class would have been. I am becoming a big fan of the "just do it" school of teaching.
( footnote )
Meilah means misappropriation of Temple property for one's own benefit. For example, if one derives benefit from a burnt offering, which is wholly consumed on the altar, he is culpable. (There is a minimum value before this applies.) One who is guilty has to repay plus a fifth (as for other property transgressions), and also bring a guilt-offering if the act was unintentional.
The mishna begins by describing certain cases of performing the sacrificial ritual incorrectly, rendering the offering invalid. This kind of error is a case of misappropriation, for the animal can no longer be used for the purpose for which it was brought. So even priests with the best of intentions can transgress this if they're not careful. (2a)
Most blessings begin with a six-word formula, followed by the text that varies. The morning service contains a bunch of these, thanking God for making us free, lifting up the fallen, giving strength to the weary, and more. (There are 15 of these in a row.) The congregation says these together. In Friday's service, the leader decreed that the congregation would chant these in "Hebrish" -- first six words in Hebrew, then chanting the varying part in English.
I previously wrote about the horror that is chanted English prayer. This isn't that. This "Hebrish" practice, I've been told when I've asked, is motivated by a desire for inclusion: people don't know the Hebrew, the reasoning goes, so this makes prayer more accessible. Sounds admirable, right? But it's misguided and, dare I say, harmful. First off, the transliteration is right there in the siddur next to the Hebrew, precisely to make the Hebrew more accessible. But, more fundamentally, this practice serves to keep people down. How are they ever to learn the Hebrew if we never do it? Are we supposed to settle for the current state and never move past it? How would I have become proficient in the Hebrew prayers if, when I was trying to grow, my congregation had kept me on the English?
The Rambam (Maimonides) famously taught that the highest level of tzedakah (charity, loosely) is to help a poor person to get a job, rather than to give him money. Giving him money sustains him for a time; getting him a job helps him break out of the clutches of poverty (we hope). The Reform movement holds this up as a key value, even placing it in the section of the siddur where we study torah in the morning. Why, then, do we refuse to apply that same principle to those who are poor in knowledge? Why is it better to give them the handout of English prayer instead of helping them to pray in Hebrew?
In the past I have remained silent to avoid the appearance of challenging our leaders. I have tried and failed to persuade leaders who do this to reconsider. Friday, when they announced this and started into those prayers, I said to myself quietly "no more" and proceeded to chant the prayers in Hebrew. The long-time member of my congregation sitting next to me said "good for you!" and joined me. We were not disruptive, but I have high hopes that maybe, next time, he'll be sitting next to someone else and he too will say "no more" and forge ahead, and maybe someone sitting next to him will follow. And maybe, eventually, we'll be able to help people break out of the bonds of illiteracy, instead of continuing to keep them down by catering to their current weaknesses. We've just celebrated z'man cheruteinu, the season of our freedom, and it is time to apply that to our people now and not just looking back at Mitzrayim.
If reading the Hebrew text directly is too challenging for some, the transliteration is readily available. Or they could quietly read the English the way I quietly read the Hebrew. (I do that when I'm at services that are above my level, like last week at Village Shul.) But let's stop telling our congregants that they're too uneducated to handle the Hebrew; that only serves to reinforce the idea until they no longer want to try.
I wonder if R. Eliezer had young children when he taught this: ok, you didn't sin that sin, but surely you've done something you need to atone for!
So I fell back to the Village Shul (Aish HaTorah), a place I'd been once before. This time, as last, I found them to be not too welcoming; this time I knew where to go in the building so the indifferent man standing at the entrance didn't hinder me, but nor did he respond to my greeting. At the kiddush (which was a standing-around affair this time, not a sit-down one), not a single person greeted me, even when I made eye contact. It can be hard for me to approach random people and start conversations; I greeted some and usually got responses but no one engaged. I don't know what (if anything) I was doing wrong; I think it was fairly obvious that I wasn't a regular, but I wasn't inappropriate in any way I could determine.
But all that said, I'm very glad I went for one reason: Tal.
Ok, I need to back up. T'filat Tal, aka the prayer for dew, is said exactly once during the year, on the morning of Pesach, in the musaf service. I had never heard it before. The Reform movement doesn't do musaf and didn't import that part into another part of the service (like is done with some other parts), and when we're in Toronto I don't always make it to Yom Tov services (but I insist on Shabbat). It's possible that I was at a Conservative service for Pesach once, and if so either they didn't do it or they didn't do anything special with it and I didn't notice.
So, this is either the first time I've encountered this prayer or the first time it registered. And it did in fact register. A resonant text (which I am unable to find online, help?), a beautiful and fitting melody (which I can't find a good version of online), and just the right amount of congregational engagement (a few words sung together at the end of each stanza) all came together into a heartfelt but not over-the-top prayer that felt entirely right to me. Wow.
And I think it needs all of those. As I said, the Reform movement doesn't do this text -- but let me predict how it would go down if we did. Because it's unfamiliar and people can't be assumed to be fluent, we would read (not sing) it, in English. Perhaps responsively, alternating stanzas. And it would fall completely flat, done that way. I'm not fluent and I'd never seen this text before either, but I listened to it in Hebrew while reading the English translation, and that worked. If I didn't need the translation then that'd be even better, but the text I read and the text I hear don't need to be the same language and that's just fine. Alas, mine seems to be a small-minority position in my movement, so I will probably not get the opportunity to experience this prayer in that setting, which makes me sad.
I had thought that this mishna would shed light on the case where one eats food that, it turns out, wasn't kosher, but it doesn't seem to be going in that direction.
I went to the Renewal movement's national kallah a few years ago, and most of what I know about their ideas and worship styles comes from that. (Much of the rest comes from reading the Velveteen Rabbi's blog.) At the kallah I encountered a lot of worship motifs that I think of as "new-age", such as drumming, movement/dance, yoga, meditation, and an abundance of creative English readings displacing set liturgy. But I also encountered well-done music that enhanced worship, and a focus on core kavannot (intentions) behind the prayers. At the time I described the kallah as a whole, including both worship and learning, as "decent with a high standard deviation".
So with some trepidation, and a resolve to leave if necessary, I went to the service. There were a couple good ideas there, but also some things that turned me off, so I'm glad this was a one-shot. I didn't walk out, but nor would I go again.
I'm not going to give a detailed chronology, but I have some observations of things that stood out:
( Read more... )