| The situation you are in sounds fixable but by no means easy. I agree with patio11 in that you need to start trying to make changes incrementally and try to presently in as positive manner to others as possible. Never try to start a conversation with the phrase "so there's this really messed up code that I'd like to fix". The classic mistake that young, hungry developers make is wanting to come in and shake things up by pointing out everything wrong and then trying to come off as a savior by fixing everything. While this may actually be the possible, it's not likely how your PM or CTO will see it. More likely you will just be perceived as a "Dwight Schrute" and regarded similarly. I would say go with your option #2 but make sure to: A) Make changes in as small of increments as possible. Don't even call them changes. It's less recognition but will be easier to pull of in the long run. B) Make sure you don't hold back on crediting yourself in the documentation though since that's what new hires will see first and should also be the first "change" that you make. C) Make sure that you communicate any changes that you make in as positive of a manner as possible at all times. This is key for reducing resistance. You will probably basically find yourself having to regularly "sell" things such as new libraries, IDEs, ect... D) If you consistently face ongoing frustration don't hesitate to send out resumes and job apps. Even if your not serious I find that getting "We'd like you stop by next week for an interview..." emails have been a great stress reducer when I've been frustrated with my job. Anyway, that's probably more crappy advice than you need so I'll stop there. Honestly if I were in your situation, from what it sounds like, I would only give myself about a 20% chance of actually being able to stay there with my sanity. |