Skip to main content

Thought for the Day: When Actions That May Engender Unintended Consequences Are Not Permitted

Another chidush (to me) from the 2011 CCK Yarchei Kallah.

There is a general principle that actions which may incur unintended consequences (eino miskavein) that are not inevitable (not a p'sik reisha) are permitted on Shabbos.  The classic example (as has been mentioned) is dragging a light bench across hard packed soil.  Dragging the bench in that case is "mutar l'chatchila"; there is no need to even try to avoid the dragging by getting someone to help you carry the bench.

On the other hand, one is not allowed to put a kettle of cold water on a fire to take the chill off, because if left too long the heat would be enough to bring the water to "yad soledes bo" (hot enough to be considered cooking on Shabbos).  R' Zucker asked: why should this be forbidden?  After all, my only intent is to warm the water (which is permitted, even l'chatchila) and it is not inevitable that I will forget to take it off on time to prevent it from coming to yad soledes bo.  At first glance this would seem to be a classic case of a davar sh'eino miskavein that is not a p'sik reisha and should be mutar l'chatchila (sorry for sounding a bit yeshivisha shprachish).

R' Zucker answered that you can only call something an unintended consequence when there are multiple consequences.  When I drag the bench, two things happens: (1) the bench is moved, and (2) a furrow is possibly created.  In that case I have a right to choose which of the (multiple) consequences I intended.  In the case of the kettle. however, I did not end up with both lukewarm and hot water; I got either lukewarm or hot water.  When there is only one consequence, I cannot say I intended a different consequence than what ended up actually happening.  In the case of only one consequence, we are forbidden to even start the activity even of it would be possible to avoid coming to an issur.

Comments

Popular posts from this blog

Thought for the Day: Pizza, Uncrustables, and Stuff -- What Bracha?

Many years ago (in fact, more than two decades ago), I called R' Fuerst from my desk at work as I sat down to lunch.  I had a piece of (quite delicious) homemade pizza for lunch.  I nearly always eat at my desk as I am working (or writing TftD...), so my lunch at work cannot in any way be considered as sitting down to a formal meal; aka קביעת סעודה.  That being the case, I wasn't sure whether to wash, say ha'motzi, and bentch; or was the pizza downgraded to a m'zonos.  He told if it was a snack, then it's m'zonos; if a meal the ha'motzi.  Which what I have always done since then.  I recently found out how/why that works. The Shulchan Aruch, 168:17 discusses פשטיד''א, which is describes as a baked dough with meat or fish or cheese.  In other words: pizza.  Note: while the dough doesn't not need to be baked together with the meat/fish/cheese, it is  required that they dough was baked with the intention of making this concoction. ...

Thought for the Day: Yetzer HaRa -- Spiritual Force of Tuma vs Physical Ta'avos

In any project planning, there are two basic approaches: top down and bottom up.  Top down starts with describing what you want done at the highest level that seems reasonable.  You then break that down into a list of things that are smaller in scope (they only accomplish part of the job) and are therefore easier to actually accomplish.  That process can is then repeated with each sub-project.  Each iteration produces a new set of smaller projects.  For any of the projects, the level above provides the "why" for the project of interest, and the projects below provide the "how" for the current project.  Bottom up starts, as it's name suggests, from the lowest level -- here is stuff I know I can do, and proceeds by asking "what can I do by putting this stuff together?" For example, I have a project to slake my thirst.  Top down would start by a requirement to get a cool drink into a container from which I can drink.  That breaks down into: (1) fin...

Thought for the Day: Why Halacha Has "b'di'avad"

There was this Jew who knew every "b'di'avad" (aka, "Biddy Eved", the old spinster librarian) in the book.  When ever he was called on something, his reply was invariably, "biddy eved, it's fine".  When he finally left this world and was welcomed to Olam Haba, he was shown to a little, damp closet with a bare 40W bulb hanging from the ceiling.  He couldn't believe his eyes and said in astonishment, "This is Olam Haba!?!"  "Yes, Reb Biddy Eved,  for you this is Olam Haba." b'di'avad gets used like that; f you don't feel like doing something the best way, do it the next (or less) best way.  But Chazal tell us that "kol ha'omer HaShem vatran, m'vater al chayav" -- anyone who thinks HaShem gives partial credit is fooling himself to death (free translation.  Ok, really, really free translation; but its still true).  HaShem created us and this entire reality for one and only one purpose: for use...