Friday, December 24, 2010

Bride-Groom Selection Spreadsheet

Soon after entering in your mid 20's you will hear a word 'proposal' more often from your parents. In most part of the India the timing for bride/groom searching is decided by the parents for two reasons
  • Arranged marriages are still very popular here
  • As you young boy or girl you will always feel that you too young to get married 

Many a times a final selection will be done based on a gut feeling of your parents and relatives. To base your decision on facts and figures I have created following spreadsheet. I personally think the selection that is going to impact your whole life should be made logically. 

In criteria or attribute column you can add up to 10 things and you can assign weighing factor to it in the adjacent column. Then you should go on replacing Name 1 to 4 with name of girls or boys your are considering as your would be. Now simply give marks to each girl and boy against each factor. The one you have with highest score should be the winner.


Click this link to open the spreadsheet - Bride-Groom Selection Process. You may require access to Google Docs to be able to use it.

I have created this sheet for one of my friend. Incidentally, he chose the lowest ranking one as his would be wife (and still living peacefully). For some people the decision will never be rational. This spreadsheet if for a group of people for whom rational decision making make sense.

Sunday, December 19, 2010

You will not learn until

While I was drying my hands I overheard two developers talking to each other. One was telling other developer an interesting story of learning better coding.

The first developer was quite famous for his coding ability in his earlier company. But sometimes even skilled people stuck. Similarly, this developer was stuck up with a problem. He spent two days on it but could not come out with solution. He scratched his head, books and at last internet but could not get any help.

Frustrated developer went to his project manager and explained what he was going through for last few days. The manager promptly came to his desk and asked for control of his development machine. He questioned developer to understand more about the problem. He took not more than 5 minutes to look for solution on Google. He copied the code, pasted it in IDE and did some quick tweaking. The problem was solved. All this was happening in front of the developer. The problem that took more than two days for him to puzzle him more was solved by his project manager in just 10 minutes.

Manager asked developer if he is satisfied with the solution. As soon as developer nodded his head the manager deleted all the code that he has just entered and closed all the tabs and cleared all browser history. It was happening so quickly that before developer could understand what’s happening his system was not more than a clean slate stuck up in the same problem.

Giving chair back to the developer the manager said, “You will not learn until you code it yourself. Now do it yourself. I just wanted to show you that the problem has a solution; you solve it.” The developer had just learnt what a good project manager means. His manager has neither put him in fix just asking for solution nor did he let him use readymade code. His manager has taught him fishing not just gave him the food.