I'm having fun jumping into this conflict. Since I'm unabashedly on one side of the argument, I feel equipped and compelled to weigh in. The work my small team

I'm having fun jumping into this conflict. Since I'm unabashedly on one side of the argument, I feel equipped and compelled to weigh in. The work my small team does is well documented, and when we execute our plans, we can click "next next etc." and everything works quite nicely. You're absolutely correct that I do not want to have an understanding of what is happening when I click next. I have a lot of other things that I need to understand. Humans for example do not have any "next" button so I spend a lot of time wrangling us. When the computer does what I think it out to do, then you're right I am not going to dig in. That's true. Inevitably I'm sometimes surprised when the computer doesn't do what I think it ought to, and I do have to dig in. Then I am perfectly happy to debug the situation. We figure out what's going on, fix it in the near term, update the documentation to address this in the long term, and then go back to clicking "next next etc." I call this productivity. I guess you could look down on me for not wanting to know things I am not getting paid to know. I look at it as saving my limited brain cells and attention for things I am getting paid to deal with.