Currently an Independent Technology Consultant, Nagaraju Pappu has more than 15 years of experience in building large scale software systems. He holds several patents in real time computing, enterprise performance management and natural language processing. He is a visiting professor to Indian Institute of Technology, Kanpur and International Institute of Information Technology, Hyderabad where teaches courses on software engineering and architecture. His areas of interest are Enterprise Systems Architecture, Enterprise Management and Software Engineering.

4 responses to “Freelancing in India – The oriental carpet shop”

  1. Kingsley

    Great anecdotes – and thanks for the advice!

    Wishing you and your family a blessed New Year – may 2007 bring you nearer to your goal…

    Kingsley

  2. Shah

    Good one sir! I learnt few important things which i need at present!

  3. SV

    Hi Nagaraju,

    It was so hilarious to read this ‘Oriental Carpet’ post and I could relate to it absolutely. I was thinking about some occasions where this has happened in my place of work. With all due respects to the consultant, here’s are some cases.
    - I have seen the consultant stuffed through the throat of VP-Engg because the consultant is a friend of COO. Now the VP not only has to accomodate the consultant, he/she has to ‘agree’ with the COO that the consultant is a great find and get things done, show results by using the consultant. And until the results are shown by the engineering team (capitalizing consultant’s srevices) the VP may not be able to justify for the budget because he/she never anticipated consultancy the first place.So, the red ink, blue ink method is a great tool for the victim who is the head of engg.
    - Again, with all respect to consultants, most of them that I have seen are out of touch with reality once they in freelancer mode for a long time unless they have been freelancing in the same domain consistently. I have met, for example, one consultant who was a security engineering head and who ventured into being a software engg consultant and then he accepted most opportunities in project management and PLC that came his way and at the end of 3 years he had lost that edge in his original core competency. But most organizations are sold to the jargon and degrees and they don’t have methods to find out how current the consultant is. Now, how does one communicate this to the consultant later? The VP engg is in a dilemma. He has to arrange for payment to someone, for something he didn’t do, for something he wasn’t evaluated to do. The internal ‘point of contact’ will be too afraid to communicate this since the consultant has great pedigree.
    - Another case that I have come across is that a consultant is signed up for a particular deliverable but there is impending reorg and restructuring that only the VP knows about and everyone has to wait indefinitely until the P&L is decided.

    Just my two cents…beautiful article though.

    Thanks
    Vid

  4. Nagaraju Pappu

    dear vid,
    you are absolutely right. the point i was trying to communicate is the way the indian culture works – we associate a certain value in delay – for example, we notice long queues everywhere – and the queue is a way of generating a lot of economic acitivity. there is a value if the train takes 24 hours to reach the destination instead of zooming there in 5 hours. we take the action when the value in delay gives us diminishing returns (for example, when i became quite a pain in the back for the VP, there is no more value in holding the payments..). This is an interesting, self organizing performance principle lurking there – though it is not obvious at the outset.

Leave a Reply