The only solution is, with sufficient bravado, you can refuse the meetings and risk getting fired if need be. If you are good and they ain’t struggling then the

The only solution is, with sufficient bravado, you can refuse the meetings and risk getting fired if need be. If you are good and they ain’t struggling then they probably will work around your preference and keep you. If you ain’t good work on that. If they are struggling then the decision is whether to stay (based on your ethics and situation) Too many meetings indicates some issue with the division or prioritization at work. Tell them if you do 2 unrelated tasks and switch between them then it is guaranteed they will get work product later than if you do one at a time. This is guaranteed. If the tasks are related it might be OK but this is a rare exception in coding. Building sheds it may be ok (lay all the foundations first). But then laying all the foundations is the task unit so again this might apply. Tell them that if management keep changing their mind, it is like calling the pizza restaurant and changing your order every 15 minutes. Food will come late. Also context switching loses time. For non technicals that don’t understand this give them an IQ test, them every 10 minutes pull the sheet away from them and swap it for a reading comp. test and then every 5 minutes tap them on the shoulder and ask about their pets. Just describing that means they should get it as almost every person had been subjected to those tests in interviews at one point.