Code reviews should be at least a chance for other team members to learn the code - and take responsibility for it. If there's a bug they should have spotted it

Code reviews should be at least a chance for other team members to learn the code - and take responsibility for it. If there's a bug they should have spotted it and the heat no longer falls entirely on you. Tests similarly are about allowing other people to change things without fearing that they will break the code you wrote. Without them the pace of change becomes very slow or very buggy. It's just working with other people that's more complex than working on your own. The meetings are usually because nobody has enough information or enough authority to get things decided. We can fix that sort of thing up to a point in many ways including the agile idea of having a product owner to prevent stakeholders annoying developers.