Great read - I am a believer in code quality as well. Unfortunately, code speed is incentivized over code quality pretty much always. I'm going to be a little

Great read - I am a believer in code quality as well. Unfortunately, code speed is incentivized over code quality pretty much always. I'm going to be a little tongue and cheek, and a little real - I've learned to look at this as an opportunity rather than a threat. Sure, Mr Product Manager, I'll deliver your project in an unrealistic time frame, knowing full well you won't listen to my feedback. But, uh oh, there are changes you want next quarter and they are not easy to implement bc the code is not extensible. Now we are seeing defects outside of the well-tested happy path, not good. I may or may not be on a different project by that time. At least I can spin that project as a "win" on my year-end review. Good luck! And this new project is fuckin cluster, but that's a good thing bc gets who gets the job to fix it (this guy). Job security! To all the developers that will inherit my mess - I should apologize but I won't bc I have been in your shoes. Think of it as a learning experience, or character building exercise. Stay positive! :) ^^ Agian, tongue and cheek. Don't like playing that game, it sucks, but it's in my best interest to play the game.