Posted by: Aadisht on: June 23, 2010
In comments, BJ says that he has a fair idea of why I think TamBrahm weddings are like ERP implementations, and asks me to confirm his suspicions with a post on this. I don’t know if he is zinking what I am zinking, but here goes.
As someone who had only seen Arya Samaji weddings (and also one sardar wedding) up until the age of 21, I was utterly flabbergasted the first time I saw a TamBrahm wedding. The whole point of Arya Samaj was that if you were going to involve yourself with religion, you should bloody well understand what you’re getting into. So if you don’t speak Sanskrit, the priest must translate everything, and give a proper explanation while he’s doing so.
In contrast, at TamBrahm weddings (and any religious ceremony for that matter – we did a bhoomi poojan at the Kanchipuram factory with local priests), the involvement of the concerned parties is minimal. They just sit around while the priests chant stuff they don’t understand.
This makes TamBrahm weddings very much like the common, or garden-variety ERP implementation. The ERP consultants are parallel to the priests. Because nobody can understand them, you have to take their word for it that they’re experts and know what’s going on. Then, there is a long and painful period in which the priests/ ERP consultants do lots of stuff that looks impressive, but nobody actually knows if it’s accomplishing anything. Finally, they collect their fees, and leave the company/ happy couple to sort things out on their own.
Extending the analogy, Punjabi Arya Samaji weddings are like installing Windows. You’re given the opportunity to read the whole end-user license agreement and cancel if you’re not happy with it. But everyone is so excited about the bling and cool new features that they skip reading it, or just nod along to whatever the shastri says and install it. After the honeymoon period, you suddenly realise that this thing is taking up far more resources than you’d anticipated.
North Indian Sanatan Dharmi weddings are like the Apple App Store. Everything looks incredibly cool and blingy, but the license agreement is completely opaque and nobody has any clue what they’re getting into.
Living in is like installing and running Linux without a GUI and only with a console. And that too by compiling the source with gcc and not from some cool Ubuntu disc or Red Hat Package manager. It seems hardcore and revolutionary, but when you get down to the specifics, is really just a lot of housework without any bling.
The analogy has now gone far enough. That’s it for the post.