I perceived the emphasis as being on the how to work. I once worked for a company that "believed" in "the one" PHP framework (developed in-house; terrible), "the one" cache (memcached - had to fight to get redis for the richer structures that we really needed; lost), "the one" DB (MySQL 5.0?), no staging environments for devs (we won a battle and allowed ourselves to run vagrant! woo), etc.
In your car mechanic analogy: you don't get to pick what cars to work on, and this is completely reasonable. But, it should be up to you & your team to pick the tools. If some idiot in the company once managed to undo a bolt with chopsticks and liekd it so much that he made it a company mandate, you'll soon be looking for another garage.
Long story short: I've seen the extreme of non-techies micro-managing technical decisions, and it is extremely frustrating. <lablab.png>
I perceived the emphasis as being on the how to work. I once worked for a company that "believed" in "the one" PHP framework (developed in-house; terrible), "the one" cache (memcached - had to fight to get redis for the richer structures that we really needed; lost), "the one" DB (MySQL 5.0?), no staging environments for devs (we won a battle and allowed ourselves to run vagrant! woo), etc.
In your car mechanic analogy: you don't get to pick what cars to work on, and this is completely reasonable. But, it should be up to you & your team to pick the tools. If some idiot in the company once managed to undo a bolt with chopsticks and liekd it so much that he made it a company mandate, you'll soon be looking for another garage.
Long story short: I've seen the extreme of non-techies micro-managing technical decisions, and it is extremely frustrating. <lablab.png>