Anup Shinde wrote:

Few in the team acknowledge that its bad code, most dont. And those who agree consider it a "way of life" - And they are not even motivated to improve - or should I say they have "accepted that way of life". (These folks are the one working in that co since more than 5 yrs.)

Sounds like you have a bad case of developers who are there for the pay check and job security, not because they want to make things better. Bad code often gets defended by the bad developers who wrote it in the first place as a form of job security. It may also just be plain stupid ignorance. If you really want to make a difference, and you feel you can improve the code base you're working on, refactor it in small increments. And then test extensively, and the refactor another small increment, and test ... wash, rinse, repeat. It may seem daunting at first, but soon you'll see changes. And once you have a set of changes that you feel demonstrates why your code is better, then show it to your "ignorant" manager. By having an actual implementation that works, and demonstrates your argument about coding practices, your team may see the error of their ways and may pay more attention. But it is imperative you have some evidence backing your argument. I was forced to fly under the radar against my managers wishes like this in the recent past, and once my argument was proven the development process evolved and was generally adopted.

|-------------------------------------------------------------------------------------------| | They wanted me to change the world, but God wouldn't give me the source code. | |-------------------------------------------------------------------------------------------|