That's because they are a non-technical manager who doesn't trust you.
I think there are two archetypes that work on the technical vs non-technical dimension:
Good: Technical, but has actually done the work (or does it currently) and is able to. In software that means they can program, set stuff up, debug things. Will be more experienced and coach, or smoothly bridges the gap between social and technical challenges.
Bad: Technical, but only "high level" and can't do the nitty gritty work but will make bad technical decisions that pushes you into a corner. Will demand concrete technical solutions instead of stating goals.
Good: Non technical, but hands off and actually trusts experts. Knows people well and how to handle tricky situations. Keeps the BS away. Approaches projects with a calm, organized fashion. Tries to take good opportunities and doesn't cling to bad decisions.
Bad: Non technical, but will constantly demand explanations, 'sell' deadlines and deliverables before consulting workers. Demands specific solutions instead of stating problems clearly. Thinks primarily about cost and efficiency instead of value and growth.