Developers And their compromises

During support project assignments or code review process often get to hear how bad the original developer developed it. If given an opportunity how they would have done it. These comments mostly get to hear from the freshers. Not knowing that the person who developed is an experienced person. Not saying that the freshers cannot make adverse comments about the skill of an experienced developer. However little they realise what the reviewer sees is the compromise that the original developer has gone through and not their original plan of action. The original plan will never see the light of day.

Good leader fashions the fresher to look at the thorn and see the rose. They teach them to be patient and remind them that the moon needs time to become full. No developer develops a deliberate bad code. I strongly believe so. Most often than not, developer follows the 'instructions' provided. The date and time stamp for a software package is not only for code versioning but also for 'circumstances' which the developer has gone through.

A good developer doesn't try to move away from the problems, because he knows very well that more he tries to move away from the problem the quicker it catches.

When the developer realises these, he graduates to become a seasoned campaigner. They looking at the night and see the day :)