True that managers shouldn't be expected to know everything about someone else's field of expertise, but at the same time, knowing nothing about anything outside of a very narrow role as a manager and being unwilling to learn anything, even basic concepts, background, or work proccesses makes for a manager you don't want to be working for as an employee and one you should be happy to avoid like the plague and let some other poor schlub deal with.

Say you're the manager of a bakery and all your reports are baking artisinal bread. It would be ridiculous if you had no idea what yeast was. Or how the bubbles got into the bread. Or you set arbitrary, unrealistic deadlines like "I just want you to take a bicycle pump and shoot air into the dough because I need some bread in 1 hour. Don't talk to me about what you're doing--I just want it done now and don't want any of your excuses." And then when the bread turns out like shit you say, "I don't know why my team can't deliver. It's just flour and water and a mixer. I told them I needed it soon and I even added double the workers to get the bread done twice as fast--plus the bike pump I got them. The bread should be done in 10 minutes with all the resources I gave them."

But especially in the tech world there are managers that are similarly naive and also unwilling to learn anything about really fundamental concepts. People are happy to help them understand and learn some basics and they're not expecting them to be experts.

But they still don't know what yeast is out how it might work after 3 years or why it might be important. Instead they just want an exact timeline to put into their report of how long a bread will take to bake, but they still don't even know what kind of bread they want you to bake just "What about that braidy bread? People like that one. Oh and this one person said they like garlic? Oh and blueberries are a superfood that's a requirement, too."