Technical manuals are an interesting style of writing. Not so much in the material, but in the way that they need to be composed. Every step must be enumerated to the nth degree, even one so small as "replace the screw you took out in step 5." During the course of my master's degree, a fellow student told a story about someone messing up an expensive piece of machinery because that particular step wasn't included in the order of operations.
Many of the best technical manuals, in fact, enumerate every action you have to take in the order the writers believe you should take them. Full disclosure: I don't always follow the steps in the order they're given. Bad Matthew, yes I know.
My point, as it relates to fiction, is that there are times where detail is good and times where detail is bad. One of the places detail is good is in the creation of the new world your characters populate. One that's bad is when you describe the specific actions characters take in a given setting.
Let me give you an example: "Moriah climbed up the ladder and pushed the trapdoor open."
Now, that sentence isn't bad per se, but it is a little more detailed than it needs to be.
A possible rewrite is "Moriah opened the trapdoor at the top of the ladder."
See how four words were cut without sacrificing any of the needed detail in the sentence? That's roughly the level of detail we should probably have in our writing -- just enough so you understand what happened, but not so much that you're overwhelmed with things you really don't need to know.
The technical writing background is beneficial because I tend to overwrite description in a lot of cases (as I was reminded in a recent critique), and thus I can better see where things need to be cut because of that. Or at least I think I can. That all remains to be seen.