Tag: scales

Chaupat Raja Cooking

While cooking my dinner this evening, I had a realisation, and not a pleasant one. I realised that the way I cook can sometimes be described as “chaupat raja” model of cooking.

The story goes that there was a town called “andher nagari” (dark town), which was ruled by a “chaupat raja”. The raja had fixed the price of all commodities at “1 taka” (not sure if it’s the same as the Bangladeshi currency).

So if you bought onions, you would pay 1 taka per onion, irrespective of the size or quality of it. If you buy a piece of rope, you would again pay 1 taka, irrespective of its length. The story, as told in my 8th Standard Hindi textbook, has a bunch of hilarious examples of the absurdities caused by this regulation.

A wall has fallen and killed a man. The chain of investigation reveals that someone sold a very large bucket for 1 taka, and the latter used that bucket as a measure for water, and thus ends up building a wall that is highly prone to collapsing.

Another story is that someone needs to be hanged, and the hangman can only prepare a loose noose because for 1 taka he ended up getting a long piece of rope that day. And so on.

Anyway, one of my wife’s criticisms about my cooking is that I sometimes “lack proportion”. Now, it doesn’t extend to everything – for my coffee, for example, I have a gram scale in the kitchen which I use to carefully measure out both the quantity of the powder and the amount of water (next in line is to buy a food thermometer so I can use water of the exact same temperature each time).

However, when cooking certain things, I use rough measures. “Throw in all the carrots in the fridge”, for example. Or “use two carrots”, not bothering about the size of the said carrots. I use “number of eggs” as measure without thinking about the size of the eggs (which varies considerably in the shops around where I live).

And that leads to chaupat raja kind of outcomes. One day, my omelette had too much onion because the onion I decided to cut that day was large. Another day, a vegetable stew I’d made turned out too sweet because there were three carrots left in the fridge and I put in all of them, though normally I would’ve only put two.

My habit of throwing in everything without measuring means that my wife has banned me from cooking several dishes for her.

In any case, what I’m trying to illustrate is that using measures in the kitchen based on numbers of something can lead to massively uncertain outcomes, and is an example of “chaupat raja economics”. What we need is better precision (even using something like “1 cup of diced carrots” is inaccurate because the amount of diced carrots a cup can hold can change based on the size of each dice. never mind “cup” is in any case an inexact measure).

Now that I’ve recognised that my style of cooking is like chaupat raja, I’ve decided I need to cooking. There is no reason that coffee is the only thing for which I should pay attention to bring in precision.

Or maybe it will just take too much effort, and the average chaupat raja outcome in the kitchen isn’t bad (the ultimate outcome for the chaupat raja was banned. The story goes that someone needs to be hanged, but it turns out that the noose is too loose (for 1 taka, the hangman got a long piece of rope that day), so the king decides to find someone whose neck fits the  noose. After much searching, someone suggests that the king’s neck is the right size for the noose and he hangs himself.

 

Slider design

Not often that I comment on User Interface, but this has a quantitative aspect to it, so I thought I’ll write about it. Basically it’s with the use of sliders on websites that you move around to determine an amount or a limit.

More specifically, I’m in the process of planning an extended weekend in Bali next month (the wife is going to be based in Jakarta for two months starting this weekend), and checking out sites such as TripAdvisor and AirBnB for accommodation. This necessarily means using a slider to determine my maximum willingness to pay for a room.

The problem with such sliders is that they’re linear. So for example, on the Travelmob page where I’m looking for villas, the price per night varies from Rs. 650 to Rs. 65000, or a factor of 100. And the slider uses a linear scale. So considering that I consider about Rs. 3500 per night as my budget, in order to set that budget I have to move the right slider (my maximum willingness to pay) way over to the left, till it almost coincides with the left slider (which determines the minimum price). And considering the small distance between the two sliders, it is easy go wrong and not be precise on your limits. A rather frustrating experience!

Instead, if the slider were to use a logarithmic scale, then 6500 would be the midpoint (geometric average of minimum and maximum), and that would allow me to pull the slider to 3500 without much hassle, improving my experience!

But then I suspect the current poor design is by design – by making it hard for you to move sliders down to low prices, maybe they are nudging customers to go for higher priced rooms?

On a different note, while on the topic of sliders, there are “fin-tech” startups that determine whether you are good credit depending upon things like the amount of time you spend moving around a slider to determine how much money you want to borrow. Quoting from Sangeet’s blog:

As an example, most peer lending platforms have a slider allowing the borrower to decide what loan they would like to take. In an excellent whitepaper by Foundation Capital on the state of peer lending, Charles Moldow shares that  the longer a borrower spends moving the slider up and down (and hence, potentially, debating her ability to return the loan), the more likely is she to return the loan. Such correlations help platforms improve their ability to curate participants over time.

This slider also looks linear, rather than logarithmic! And so it goes.

Update

AirBnB actually uses a logarithmic slider! Whatay!

Fractal life

Recently I finished reading Mandelbrot’s The (mis)Behaviour of Markets for the second time. Fantastic book. I think it is a must read for people who are interested in financial markets, and especially for those who work in capital markets. While it stays away from equations and “math”, and prefers to use pictures (or cartoons) to illustrate and show concepts (a method I definitely prefer to obscure math), it does raise a lot of very interesting fundaas.

So last week I was feeling stressed out. I realized that I had worked too hard on Wednesday and Thursday hence I got stressed out on Friday. A couple of months back, I took a couple of days of medical leave because I was stressed out. I reasoned that was because I’d pushed myself too hard the earlier two weeks. And thinking about all this today, I thought the incidence of stress has gone up over the last couple of months. This, I reasoned to pushing myself excessively for over a year now. And if I were to analyze my today’s work, I could probably say that I pushed myself too hard in the afternoon and hence got stressed out in the evening.

Same pattern, you see. At different scales.You get the drift, I guess. And stress is just an example I took. If I think about how my louvvu for my wife has evolved, again same pattern. There is a “global pattern”, and that same “global pattern” repeats itself over shorter intervals over the last two years. Irrespective of the quantum of time I look at, I see that same “global pattern” stretched or compressed to the appropriate time scale. In other words, love is also a fractal.

You can see fractals all around you. You can see self-similarity everywhere. And yet, even when you have small samples. you instinctively try to model it as a normal distribution. Without realizing that the “normal” distribution in life is the Power law.

Simplicity and improvisation

While writing my previous post on the film game, I was thinking about simplicity and improvisation. About how if you seek to improvise, in order to improvise well, you would rather choose a simple base. Like how the simplicity of film aata allows you to improvise so much and create so much fun. I was thinking about this in several contexts.

This concept first entered my mind back in class 11, when a mridangist classmate told me that for all music competitions, he would choose to play the aadi taaLa. His funda was that the simple and intuitive 8-beat cycle in this taaLa let his mind free of conforming to the base and allowed him to use all his energy in improvisation.

Thinking about it, though I have little domain knowledge, I would consider it very unlikely that a Carnatic performer would choose a vakra raaga for the “main piece” of a concert. The main piece requires one to do extensive alaap and then taaLa and requires a lot of improvisation and creative thinking on the part of the performer. Now, a vakra raaga (one where there are strict rules governing the order to notes) would impose a lot of constraints on the performer and he would be spending a large part of his energy just keeping track of the raaga and making sure he isn’t straying from the strict scales.

Starting from a simple easy base allows you to do that much more. It gives you that many more degrees of freedom to experiment, that many more directions to take your product in. If you build a sundae with vanilla ice cream, you can do pretty much what you want with it. However, if you use butterscotch, you will need to make sure that every additive blends in well with the butterscotch flavour, thus constraining your choices.

When the base for your innovation is itself fairly complicated, it leaves you with little room to manouever, and I’m afraid this is what occasionally happens when you are into research. You specialize so much and start working on such a narrow field that you will be forced to build upon already existing work in the field, which is already at a high level of sophistication. This leaves you with little choice in terms of further work, and you end up publishing “delta papers”.

Similarly in the management context, if you start off by using something complicated as your “base framework”, there aren’t too many things you can put on top of it, and that constrains the possibilities. There is even the chance that you might miss out on the most optimal solution to the problem because your base framework didn’t allow you to pursue that direction.

It is all good to borrow. It is all good to not reinvent the wheel. It is all good to stand on the shoulders of giants. However, make sure you pick your bases carefully, and not start on complicated ground. You will produce your best work when you give yourself the maximum choice.