Being a manager

is about managing status quo. Thats the quote i read somewhere. So, if you like stability and have the courage to fight the changes around, only then should u embark on this. (Ofcourse after some years u will be pushed into this, so start building courage anyway).

If you get into ur shell everytime something stressful or dynamic situation comes your way, then u are spoiling ur chances. You need to communicate more with your team members, more than any two team-members communicating with each other. Everytime u take a decision, go out and talk about it. Let there be open discussions. Otherwise you are just waiting for people to look at negatives of the decision.

And to the contrary in every company, i see executives, managers rushing into their shells everytime something important is happening to the team. Well, no body asks u to write code as a manager, until unless their are far too less bugs and QA is skeptical. And most of the times in the name of laissez faire or macro management u leave individuals onto downhill paths. And only at the year end u come out as a great judge of people, throwing ratings and distributing the booty. Atleast take time to explain the decisions.

Software Job engagement

.. is indirectly proportional to inverse of experience square.

Well, My first job was 3 yrs and i left that job because i found something better. I was happy with my old job too. My second job was for 4 yrs. And i left it because i was fed up with the job. And then 1 yr. And now it looks that in less than a year i can realize that current job is not anything great.

Hmmm ... Lots of other friends of mine have been able to hold on to a job, because they have accepted that job is not going to give them any great satisfaction. So they concentrate on other aspects of life.