These experiences mirror my own in an uncanny way (recently made team lead, 3-4 devs, just started code reviews) and found all of this information extremely use

These experiences mirror my own in an uncanny way (recently made team lead, 3-4 devs, just started code reviews) and found all of this information extremely useful. I would add that discussing how much mileage can be estimated on the current stack is important as well. Good code can still be dangerous if someone in the team knows or feels they are only going to get 3 months out of it before dependencies will change and will need to update it again. I've found discussing sustainability from time to time helps to figure out who is checking in their code just to make it to the next day and who has an eye towards creating a low maintenance product. Life pressures can cause the best devs to live one day at a time they just need the proper forum to express it to the whole team. Sometimes it just simply gets forgotten or lost in the shuffle- the fact that library or API "X" will no longer be available.