Meetings can help projects by sharing knowledge but can also kill projects if they steal time away from development. The author leads a team of 50 Java developers working on 25 projects and 8 customers, with over 300,000 lines of code. He argues that meetings should respect programmers and blame projects, not people, and that a project's goal is to acquire knowledge, not bring people to meetings, as meetings can steal valuable time away from advancing the project.