Communication. Whether it's communicating about bugs, tickets, issues we've encountered, bugs or talking about how drunk was someone this weekend or where we'l

Communication. Whether it's communicating about bugs, tickets, issues we've encountered, bugs or talking about how drunk was someone this weekend or where we'll go for lunch. I've seen lack of communication cause issues that snowballed into huge combination of hours and money spent * stress and willpower. If you're going to lead the team, don't be one of those silent guys that nobody wants to ask something because they know they'll get a CS lecture and "mental negative points". Be accessible to your team, create a positive, relaxed atmosphere, be open to ideas and suggestions and with good communication even the worst crunches will pass like nothing. Other than that: * Proper git usage * Defining how we work (architecture, style, plugins) * Code reviews * Static analysis - no people blame, machine told you that code sucks