Working for money

One of these days during lunch at office, we had a fairly heated discussion about why people work. One guy and I were of the opinion that the primary reason people work is for money, and everything else is secondary. The third guy, who among the three of us perhaps works the hardest, argued that “people who make a difference” never work for money, and that it is only “ordinary people”, who have no desire to “make a difference” that work for money. He took the examples of people like Steve Jobs and a few famous scientists to make his point.

Now, while I agree that money is the primary reason I work, and which is what I argued that day during lunch, I disagree that the end-of-month salary credit tells the whole story. The way I see it, you need to take a longer-term view of things. So while the short-term money you make is important, and affects important decisions such as quality of short-term life, a more important thing is sustainable returns. While you do your work and get that end-of-month salary credit to bolster your bank account, an important thing is about how much the work you’re doing now will contribute to your income later on in life.

Digression 1: I keep oscillating between wanting to retire at forty and wanting to retire at sixty. And I must admit I haven’t frankly decided which one is more suitable for me. This analysis is more relevant with the retirement at sixty model (which is what I think I’ll end up following, health etc permitting). End of Digression 1.

Digression 2: Not so long ago, some people in my firm wanted to recruit “software engineers from IIT with two to three years of work experience”. Being one of the “CS guys” around, I interviewed quite a few people for that role. Their CVs indicated that had we “caught them” on campus, they would have been sure hires. But two years at a software services shop, I figured in all cases, had made them “rusty”. Spending all their time in mind-numbing activities (like building UIs), they had failed to build on the skills that would have been useful for the higher-up-the-value-chain job I was recruiting for (finally that team went to IITs and got a bunch of campus hires. They gave up on lateral hiring altogether). End of Digression 2.

Those two digressions weren’t particularly meaningless. I guess you know where this post is headed now. So, the thing with a job is that along with the short-term benefits it provides, it should also help you build on those skills that you think you can monetize later on in life. Every job (most jobs, really) teach you something. There is constant learning everywhere. But what matters is if the learning that the job offers is aligned with the kind of learning that you think you are geared for, which you think you can monetize at a later point of time in life.

I still claim that I work for money, but just that I take a longer-term view of it. And I strive to learn those things on a job which I think will be helpful for me in terms of monetization at a later point of time in my life.

 

When will people come?

So I was trying to estimate how many of my invitees will attend my wedding ceremony and how many will attend the reception (the former is at noon and the latter the same evening). While a large number of people have kindly RSVPd, not too many have really mentioned which event they’ll turn up for. So it’s my responsibility to somehow try and figure out how many will come when, so that the information can be appropriately relayed to the cooks.

Personally, if I’m attending the wedding of someone I don’t know too well, or a wedding I’m attending more out of obligation than out of the desire to be there, I prefer to go to the reception. It’s so much quicker – queue up, gift, wish, thulp, collect coconut, leave. The wedding leads to too much waiting, insufficient networking opportunity, having to wait for a seat in a “batch” for lunch, and the works.

Again, I hope that most people who are coming for my wedding are coming more because they want to attend rather than looking at it as an obligation. Actually I was thinking of a wedding invite as being an option – it gives you the option to attend the wedding, but you pay for it with the “cost” of the obligation to attend. In fact, over the last few days, I’ve felt extremely guilty while inviting people whose weddings I bunked (for one reason or another).

That digression aside, what upsets estimates for my wedding is that it’s on a Sunday, when more people will be inclined to come in the morning rather than at night. For one, they have the day off. Secondly, usually people like to spend Sunday evening at home, ironing clothes and the like, preparing for the grueling work week ahead.

And the fact that the venue is on the northern side of Bangalore, while most of my invitees live in the south (the fiancee and most of her invitees are in the north) makes me want to increase my “lunch” estimate and decrease the dinner estimate. And then the fact that I’m getting married on a seemingly “auspicious” day, when there are lots of functions all around, makes me wonder if I should discount the total attendance also.

After the wedding is over, I’m willing to anonymize and share the spreadsheet I’ve used for my estimates. Ok you might think I’m a geek but what I’ve done is to put an “attendance” probability for each event for each attendee, and then taken expected value to get my estimates. As I write this, I think I should take standard deviation also, and assume the law of large numbers (yes I’ve invited a large number of potential guests) in order to provide my in-laws (who are organizing the whole event) 95% confidence intervals for number of guests..

Anyways, I just hope that my (and my in-laws’) estimates are right and we won’t end up erring in either direction (shortage of food, or wastage) by too much in either direction. And the costs of the two (localized costs – as hosts, our costs of food shortage (in terms of reputation, etc.) is much higher than cost of wastage; though from global sustainability perspective it’s probably the other way round) have led our solution of the Newsboy Problem to be conservative in estimate.

And yesterday I was suggesting to my in-laws that after the wedding lunch, we can revise the estimates for dinner to M – X where M is the total number of guests we expect (counting double for people who we expect to attend both lunch and dinner) and X is the number of people who had lunch. It’s important, I think, to use as much information as possible in making decisions.