[micheljansen]

You ask "what else besides writing code or managing people" and mention prototyping & creativity: have you considered moving into product design/UX or product management?

After working as a developer for a few years, I got a bit disillusioned with "building and fixing things all day" as you say. I now work as a User Experience architect and am still involved with building and fixing things, but in a very different way. I still write code, but mostly to prototype ideas and collaborate with developers.

A broad understanding of various technologies and lack of specialisation/investment in particular frameworks is a plus, as you can understand what's required, without getting bogged down in details. You can take a leading role, without having to be anyone's boss.

Not sure if this sounds attractive to you, but it works for me :)

[jbl]

Product management could be a great fit for the OP. However, PM means a lot of different things. Even within one company, day-to-day experiences of PMs can vary a lot depending on the nature of their product or product-area. Some PMs have very broad exposure to the company when bringing a product or feature to market. Other PMs are more marketing and sales leading, while still others focus on learning/developing requirements and writing specs.

My advice to the OP is to set titles aside for a moment and focus on what it is they like doing and where they want their career to go, then work from there to find a position that suits. It might be called product management, product marketing, or it might even be called lead architect or CTO.

The one piece of advice I'd give, though, is that for such broad ranging interests, I think one will need to relax and give up a modicum of direct control, particularly for larger more complex projects. What is it they say about product management? All of the responsibility and none of the authority? Or, more prescriptively, lead by influence.