I'll just rewrite this paragraph and it will answer the question for the author: An experienced engineering manager anticipates the secondary effects of every

I'll just rewrite this paragraph and it will answer the question for the author: An experienced engineering manager anticipates the secondary effects of every change, and weighs tradeoffs between a multitude of approaches in solving problems. By continuously modeling software systems, the organization they work for, and customer behavior, the most effective managers readjust their approach to problems daily. This is a great example of what good engineering managers do because after a certain size of a project, one person can't build while also keeping all the downstream externalities in their head. But wait! Microservices and self documenting APIs will fix all this right? Nope - people and process management is as important here as it is on a car assembly line. To adulterate a quote from James Madison: If [programmers] were [perfect robots], no [management] would be necessary.