I follow the advice of Greg Crenshaw: Schedule everything in your calendar. That includes coding. Time before and after meetings for preparation and review. Rea

I follow the advice of Greg Crenshaw: Schedule everything in your calendar. That includes coding. Time before and after meetings for preparation and review. Reading and answering emails... You get the drift. Be generous with the estimates. And personally I liked to push the responsibility back to the organiser of the meeting, if there is a conflict with the schedule, i.e. affects my deliverables: sure, I can attend that meeting but that means X gets delayed. Is that okay? Like many engineer-minded people, I consider (possibly wrongly) meetings as a waste of time. This way, I don't have to weigh meeting time against coding time myself. And everyone is aware of the trade-offs needed to be done.