No problem - glad I could help shed some light on things. I've recently come to that conclusion about work - currently I'm best when I get to make strategic decisions, whether it's about which client work to take, code architecture, or just about anything really.

"Being given a list of specs and then coding to the specs is just not my kind of thing" I bet creating the architecture for how the problem will be solved in the first place is more your kind of thing. I used to think every programmer wanted to be an architect, then realized a few years ago that wasn't the case.

Hang in there, and keep working at it!