Skip to main content

Thought for the Day: Acquiring Your Olam HaBah in a Moment Takes a Lifetime of Work

The mishha in Avos says to be as careful with "light" mitzvos as "important" mitzvos, because you don't know how the reward is calculated. There are several different explanations of the lessons one is meant to learn from this mishna, but the unifying theme is that we just don't know how the final דין וחשבון/accountability will be computed. I had an amazing experience at work today that brought this mishna to life for me like never before.

We had our quarterly group meeting today, attended also by the heads of our internal customers. (The group I work for by and large provides software tools that allow that group to do the work our external/paying customers need done.) The head of that group showed a slide of all the wonderful things we had done for them over the last year. The list included very large features, some required months of effort and as many as a dozen people involved. People had been given special recognition awards for some of those projects. On the list were two projects I had worked on. One project, while I was the technical lead, there were another couple of developers and it took us several weeks. I asked if it really made a big difference to our (external) customers and he enthusiastically replied in the affirmative. It was saving our customer time, money, and aggravation. That was nice to hear.

The other project, though, I did by myself. It took about four hours; maybe eight hours when you include all the meetings to iron out the details. It was not really on our list of priorities, but I was about to go on vacation and I figured I could get it done and deployed to production before I left. Low risk, easy coding. What we call in the industry "low hanging fruit". Given the context of the other items on the list, though, I was shocked to see it there. So I asked about it: "You know, I am surprised to see that on the list. It really only took me about four hours." They went on to tell me how important it was to them, how much their customers liked it, and how even the legal department liked it. In fact, the manager told me that he had been given a charge to save a half a million dollars that year, and my (little) feature had saved the $200,000!

So... in one day's work this year, I provided a benefit to my company that more than justified my cost. I am still a bit stunned how much impact it made. But, in truth, it didn't take me just four hours. It took me 65 years of preparation, which enabled me to make the right decisions and to be able to write the literally half dozen lines of actual code. As we come to the end of 5783 and prepare to meet our King and sign of for, the Good Lord Willing, another year -- it's good to keep in mind that we really don't know what are big, important mitzvos and which are "little" mitzvos. But it is not just that the mitzvos themselves have value, they also prepare us and train us to be able to do more mitzvos on ever grander scales.

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...