Subscribe to Software Autopsy        RSS Feed

The pouring water after the fire syndrome

Icon Leave Comment
I usually love to take a shot at the people above me in the chain of command. After observing their behavior for quite some time, it hit me that these people wait till everything is done, and then pass comments and suggestions. Usually these comments and suggestions are like "this should have been done some other way" or "I didn't want it to be done this way" or "Can you customize it more, so that all I have to do is click a button and the software should do the rest and things like that. I always wondered why do these people wait till the project is over and then pass their comments. Why can't they review the code/project regularly and suggest things while they review it. Why can't they have a discussion and suggest first how to proceed. I guess every successful manager/team lead does that. Just imagine you write real great code and you get a cold shoulder, how annoying it would be. You are proud of your code, all it take just few changes, which are very easy by the way, very minor when compared to the things it can do for you, or how seamlessly it can work. It is not that the whole process can be automated, when a programmer can come up with a nice fantastic code, I guess the programmer can write few more line, but at what cost? Is it really worth the trouble? In all fairness I am really not sure if that is correct. It is my view any way. The point that I want to bring out here is that why wait till the things are in the complete and then suggest "oh you should have done it like this", instead be pro-active and suggest before the coding starts, put your idea forward and suggest how to design and review in a environment in which ideas can come out easily. Don't review in a environment where your subordinates just agree with you because either they hate you, or they are scared of you because you bully them, they just agree with you because they are seeing a easy way out of the situation and say I am glad it over, relief till the next time. be flexible, if you have a valid point, suggest in such a way that the people listening to you would agree with you because there is logic in what you say, and give your subordinates chance to think and say "Yes you have a valid point, I will see how it can be done", but if you try to impose your ideas, no matter how good they are, it is not a good idea. If you have a real good idea, make people see the logic and the reason and make them see why it makes sense to implement the idea, which is good both for you and the project. I have worked a with a nice manager, who is very good at handling people. Also my dad is a great manager, he handled around fifty people, and I keep taking lessons from him on how not to manage. he field is software and hardware reliability, and believe me when I say this, though he not a programmer, he has helped us (few people and me) in programming, how to implement the logic in a language, and found out few loopholes in the software, basically making us looks like fools, till then we though we were great programmers. He simply guided us on how the software can fail. Any way the point here is if managers/team leads can come down from their "thrown" and get their ego in control and see, and make the work environment friendly, by friendly I don't mean they should sit and booze or smoke together and make jokes, by friendly I mean, it should be friendly to a productive discussion, rather than argue uselessly and have everyone shout, and make faces at each other, and in the end everyone hates the team lead/manager, end up either depressed because they have to work with such a manager/team lead, or quite the job.

So it is like you see there are sparks which could lead to fire, but you ignore the sparks and let the fire start and spread around a bit, create damage. Then argue about what caused the fire, and how to put off the fire, by this time the faire has done more damage, then they go looking for extinguisher and put off the fire. If they had just been careful initially, the fire would not have spread in the first place.

Too much ranting for one day

0 Comments On This Entry


October 2017

151617181920 21

0 user(s) viewing

0 Guests
0 member(s)
0 anonymous member(s)

Recent Entries

Search My Blog