I think it's less about the skill and more about the development process. When your manager comes to you and want feature upon feature added to an existing proj

I think it's less about the skill and more about the development process. When your manager comes to you and want feature upon feature added to an existing project that once was written without any basic requirements laid down, the code is going to turn to shit pretty quickly and nobody is going to care about it. The process is broken. One of the reasons why open source is good is because you associate your code with your name. You take personal responsibilith for it. At a company where developers have come and gone over time, that doesn't happen. Now, how you approach this matters. You can either become one of those who don't care, you can start to roll the stone uphill or you can seek greener pastures. It's all up to you. The people you work with sound like they don't care for things as long as it works. Do you want to become like that?