"I am webby and I think webby" - AjiNIMC aka Aji Issac Mathew - "I thought and I wrote".

 AjiNIMC logo - Aji Issac Mathew I am Aji Issac Mathew also known as AjiNIMC at various forums. I am webby and I think webby, being a part time blogger, this blog is a documentation of my experiences and my learning.
Blog Stats (06 June 2008): There are currently 306 posts and 1100 comments (and 397,307 spam comments), contained within 17 categories.
RSS for Aji Issac Mathew's blog 
  I am into professional Web Marketing services which includes Web marketing strategies, SEO/SEM, Content Designing, Web Designing for usability, conversion improvement and various other things. There are limited availability per month. We don't take too many clients but we make sure that all our clients get their share of success. I worked on in-house sites for over 5 years, now is the time to help others with my experience. I have a great team helping me achieve this. A very creative and experienced team. I write at http://www.dawebmarketing.com/kb/clients/. Contact aji.issac (at the rate) digitalavenues.com and get your share of success.  

 Home >

Manager vs. programmer - My Story

Oct
2

(do not forget to read my other stories at digg)

I am working with R&D team, exploring new things, doing programming, optimizing codes, handling servers but on the other hand I have 5 to 6 teams which summate to 40 people. Handling people is art so is programming, each module demands time so does each member. The problem was not work, I can work both as a manager and a programmer but it was the thinking, a manager’s mind and a programmer’s mind. Do managers work? Do programmers like documentation? I spent almost a month with my boss which helped me improve as a manager cum programmer, in tech terms a Techno-Manager.

Techno part
A technical guy tries to solve problems and is concerned more with a module or in bigger view with a product. He wants to make it the best and so he works. He trusts no one but his mind while programming. He studies more to acquire knowledge. He feels bad if he doesn’t know the answer. He wants to be the best. He thinks he can handle things on his own. Appreciating others work is a little difficult as he knows he could have produced better. He feels meetings, discussions, documentations are not that useful. He alone can give it a fight and make things happen. He creates slow but long lasting impressions.

Manager part
A manager identifies the problem and tries to find the root to eliminate such chances for future; he documents it and involves people to find the best solution. He fixes it or asks a team to fix it forever with a complete documentation. He wants the things to be the best so he trains and hires best people as he know his own work will never make the project succeed. He trusts people and pushes more responsibility down the line that he can take more. He keeps his mind free and uses others knowledge to make things work. He knows someone in his team will know it better and feels proud to promote him while answering it. He wants to have the best team and he is not better than his team. He is there to co-ordinate and is incomplete without his team. He appreciates every work as he knows it will produce better work. He knows meeting will transfer knowledge, discussion will help him understand the team’s problem and documentation will help his team operate without his time. He feels helpless without a team. He strikes hard with quick but short impressions.

I wish I could write more things on both part but as we say neither I am an ideal communist nor a complete congressman. We have both the qualities but changing our thinking process is very important.

I believe a programmer in himself is more efficient than a manager but a manger is more effective that a programmer. I prefer to be more effective rather efficient.

10 golden rules:

  1. Start developing people.
  2. Push the responsibilities (just not work) down, you will see people performing much above your expectation. Believe in people.
  3. Improve culture, document things. Do not teach one but teach the one who is with you now and one who will join you after a year. This can happen only with documentation.
  4. Hire best people (the most imp thing for sure), fire bad ones. Do not waste time on inefficient people. This will help you and the person too.
  5. Appreciate people and a 24 carrot manager can create many good programmers.
  6. Do not teach them how to do, tell them what to do.
  7. Only words will not motivate people in long term but yeah for short team do speak out motivational words. Share the dream, just sharing work can give you a worker but sharing vision will gain you a missionary if not visionary.
  8. Never under-estimate yourself, people are not great because they are born like that but they are great because they are molded like that. (I am not starting the debate again, “Are leaders born or developed�?, I know I debated hours on it).
  9. Share your problems with others.
  10. Paper and Pen will work better than a 1GB laptop to solve complexities.
This post was written by AjiNIMC aka Web Kotler at 11:08 pm under category Human R(




9 Comments »

  1. Again a great post but i’m confused with the second point,
    coz i recently faced problem by believing one person and pushing responsibiliteis….
    but i must say this is the best post….
    I’ve learned many things….. and will learn contonuosly….



    Rajesh Kumar Rana on October 3, 2005 - 3:20 pm @ 3:20 pm

  2. if we do not push responsibilities down we won’t go out for fishing the way your boss go. You can relax if you know there is someone who is working harder when you are not there.Develop people, motivate them and make a atomsphere where you can enjoy the work. Smart workers are more effective than hard and effiecient workers.

    With fishing I remember a famous quote,

    “Give a man a fish and he’ll eat for a day. Teach a man how to fish and he’ll eat for a lifetime.” Training others is good for you, good for the person who gets it and for the company an overall gain.



    AjiNIMC on October 14, 2005 - 9:02 pm @ 9:02 pm

  3. [...] http://idealwebtools.com/blog/?p=29#comments [...]



    iLearn » Manager vs. programmer (From Aji) on October 17, 2005 - 7:43 pm @ 7:43 pm

  4. I learn lots of things from you, I’ve decided of make a separate blog for those things that i learn and keep it to retain it,
    http://www.rajesh.webpress.com



    Rajesh Kumar Rana on October 17, 2005 - 8:08 pm @ 8:08 pm

  5. oh really :) … thanks, you keep me motivated to do more blogging



    AjiNIMC on October 17, 2005 - 8:16 pm @ 8:16 pm

  6. I’m serious :)



    Rajesh kumar Rana on October 17, 2005 - 10:47 pm @ 10:47 pm

  7. [...] This is an extension of my previous post on Manager vs programmer. Leaving programming was a little difficult for me but then with time I am able to survive weeks without it. I haven’t left it altogether as I keep trying the new technologies with a bit of programming. Also I keep transferring my experiences with code management and optimization to upcoming programmers and leaders. [...]



    My Abode » Manager to Leader - Your call on July 19, 2006 - 11:44 am @ 11:44 am

  8. Doer vs. Manager…

    I remember one of my first confusion on the debate between being a manager and a doer.  That was……



    EntrepreViews on January 1, 2007 - 5:13 am @ 5:13 am

  9. [...] This will be the time when you will have to slowly leave the things you are comfortable with, and learn to accept new responsibilities.  Here is another excellent post on how to transition between a programmer and a manager. [...]



    Reflections of a BizDrivenLife » Blog Archive » Doer vs. Manager on January 1, 2007 - 5:57 am @ 5:57 am

RSS feed for comments on this post · TrackBack URI

Share your thoughts

You are visitor number