* Code review and care. * Always leave code in a better state than you arrived. This project is big, it's definitely not your average webapp express node.js yo

* Code review and care. * Always leave code in a better state than you arrived. This project is big, it's definitely not your average webapp express node.js you see these days. From my experience in projects this big with a big team, there's absolutely no better solution than reviewing code carefully and caring about quality. I was in the same situation as a consultant a few years back and the rule to leave code better than you arrived at it is a real trigger to most people that respect what they do. I'd say that the VP ENG should be involved in the process and set some rules for what is acceptable quality and what isn't. One more thing Everyone knows a smell, every single member of your team has some piece of code he/she saw that doesn't make sense. Keep a document with all of these and just make sure you scratch them off EVERY single day. Stuff like: * User Creation is using LOCK on table_x and it shouldn't * Form submit code is too complex, need to be better * Extract component X into a microservice etc... If you go through a list like this and fix things one by one, you'll be better off in a short amount of time. Don't try and take it all at once, create manageable consumable pieces that your team can relate to, understand and get behind. Good luck