To Indianise a Cartoon, please dont

I saw 2 curious editorials about importing Archie to India in Point - Counterpoint in Times yesterday.

If I were to take sides, mine will be on the side of not trying to Indianise anything.

Simply because of the variety and colours that India offers, cannot do justice on any “Indianise” process however clever.

Secondly my personal experience with 2 of my kids with Cindrella, which they just don’t relate.

While fables are most easily transferable across cultures, (see how Panchatantra got the reach and derivatives across cultures)

stereotype transfers (like this Archie transfer) from another culture will fail to convey anything or even be mildly entertaining.

Archie will be in for a rude shock in India…

Brain Drain ++

Dr Dan http://it.toolbox.com/blogs/dr-dan/lets-all-play-the-brain-drain-game-24159 here notes about brain drain, the “process” and the act of “capturing knowledge” with a luxury of time.
The real problems in a “typical” software services company where you do not have much future visibility on either people or the knowledge need are
the above plus
a time compression
and key people leaving repeats itself before the close of a contract (not so often if you are a lucky PM)
This is in addition to trying to optimize a firm for the one $$$ variable (reduce costs) when “billability” is given the most priority over all other parameters (suitability, contextual continuity, quality …) and further brain drain is orchestrated deliberately as well.
Any strategies, suggestions???

Phone Chord

The length of phone chord in enabling support engineers to work knowledge effectively has to be applied to AMS projects or in cases where continuity between dev to support teams. So the seating arrangement has to be designed to decrease barriers in face to face communication

From The Social Life of Information