Ravi Mohan's Blog

Saturday, September 29, 2007

The Symbolism of the Bended Knee

After a friend informed me that her fiance had proposed marriage on bended knee, I decided to look up the symbolism.

here, I found

"..... There is no clear historical origin of the idea of proposing with a bent knee, but the gesture bears striking resemblance to many other ceremonial situations, including:

  1. Kneeling during prayers and other religious ceremonies, including wedding vows for some faiths.
    • Kneeling while proposing, then, has the same solemn and spiritual connotation.
  2. Knights kneeling while being awarded honors from kings and queens.
    • Offering or accepting a marriage proposal is just as much an honor as any medal or award.
  3. Bowing in supplication before a victorious enemy, typically as a gesture of surrender.
    • Committing to a relationship is surrendering oneself to being part of a couple.
  4. Kneeling to genuflect when entering a church or temple.
    • Again, proposing on bended knee is a sign of respect and spiritualism.

On applying some (no doubt unromantic) analysis, the first two "interpretations" seem distasteful. In both cases there is the distinct notion of kneeling to someone you have acknowledged as a superior power.People don't kneel to equals. When was the last time you knelt to your peers (or your manager for that matter)?.

If the fourth reason were valid, both parties should kneel. (Going off on a tangent I wonder.. if the roles were reversed, would feminists see this as a "patriarchal custom to oppress women"? They do seem to take umbrage at changing surnames etc).

That leaves the third reason - "gesture of surrender to a victorious enemy". Hmmmm.....Interesting.


Seriously though, does anyone know what the kneeling is supposed to symbolize? This is a Western custom (though gaining popularity among the urbanized youth in India too or so I hear) so its origins probably lie somewhere in medieval Europe. I couldn't find any concrete information.

Thursday, September 20, 2007

Saluting Randy Pausch

First read this (via news.ycombinator).

Then see the streaming video. It is terribly slow and broken up on a typical Indian internet connection but just see it anyway. You'll thank me afterwards.

If you are a parent, a spouse, a teacher (of any subject), a student, a programmer, an artist, a designer, a public speaker, just see it.

Dr Pausch, I have never met you but you just changed my life. Thank You.

Update: The video is on YouTube in ten pieces. This is much better than CMU's streaming video, because in these you can load the full video before viewing, go back and forth etc.

Tuesday, September 18, 2007

The Lame and the Blind - Proofs And Code in research software

There is this old story about a blind man teaming up with a legless man. The blind man carries the legless man on his shoulders and provides the locomotion while the sighted cripple tells him where to head.

Similar divisions of labor exist in enterprise software (think "developer" and "analyst") but this two fold division of labour is exacerbated when one focuses on research software. Here the scientists are the "sighted folks" who know where to go but can't move and the developers are (ideally, as we'll see later) the folks who know how to move the project forward by writing code, but don't have the requisite mathematical/scientific skills to navigate and choose one direction over another.

Earlier today, I was talking to a scientist trying to move a multi million dollar machine learning project forward, who was feeling hamstrung because it was impossible to find a few people who could follow advanced calculus and also write good C code.

Unlike in the folktale, a real life arrangement consisting of a blind man and a cripple would be very inefficient, with the occasional fall, not to mention the constant stubbing of toes and odd outburst of swearing. But equally, nothing in real life mandates this kind of "pairing". Nothing prevents a scientist from learning how to code (except a feeling that coding is a relatively "blue collar" activity) and nothing prevents a developer from learning the requisite maths and science (except that most developers, especially the enterprise/agile/dsl types either don't have the caliber to learn hard math or think erroneously that these skills are beyond them or just don't want to work that hard).

The few folks who do master both proofs and code, can and do make a tremendous difference. The very best people in every research area that incorporates software and maths are very capable scientists/mathematicians and very capable programmers. Peter Norvig is an example. As is Donald Knuth. Or Manolis Kellis. Or Yann leCun.

If you are running a research software project you'd want to staff it with high level multi-class (think dungeons and dragons) scientist-mathematician-developers. Unlike in D and D specializing in one area does not need to involve trading off the other.

After all the lame man/blind man arrangement is not the best possible one. The best (and normal) situation is having two (or n) people who can both walk and see.

Tuesday, September 04, 2007

Erlang is the new Ruby

There is a particular type of programmer who tries to keep up with the "coolness" crowd by jumping on to the latest bandwagons and hanging on for dear life (till it is time to jump again). The word "fanboy" doesn't quite describe these folks but it gets some of the nuances right. The key characteristic is that they talk a lot about what essentially they don't really understand.

For a while , the fad was ruby. "Ooooh look we can use select instead of a loop" "Oooh everything is an object". Then it was creating half baked "DSL"s, especially in the context of Rails.

Now Ruby seems to be losing some of its sheen, and the lemmings are migrating to Erlang. Now, Erlang is a very powerful language that is worth studying and it has been around for the last twenty years or so, but the next time I meet someone "evangelizing" Erlang, without the faintest idea of how functional programming, pattern matching or concurrency really works, I am going to do something nasty.

Don't get me wrong. Erlang is well worth studying. But first write a 10,000 line+ non trivial program in it. Create an open source library or two. Submit a few patches. Then try to convert the heathen. But I guess if you were to do that you wouldn't be a fanboy anymore.

Ahhh. Choices.