There will probably be three more submissions just like mine before I hit submit, but you should very likely consider a transition to a management / liaison role.
There are a variety of fields that benefit from code-savvy people that are able to communicate effectively and that have just a little bit of initiative, namely:
- project manager -- there are a lot of definitions for project managers, but the simplest I think is the guy who sits between upper management and the engineers to ensure that project deadlines are met by removing obstacles for the engineer. As a developer, your unique insight here is in the ability to anticipate roadblocks and be able to remove them, as well as not having to have things explained to you three times before you can act. As a project manager, you'll be privvy to upper management's goals and directives earlier, be in a position to shape the project, and tangibly demonstrate how your contributions streamline the development process. Often-times, as engineers, we only hear "We need feature X", without an explanation for why we need feature X, and a lot of times, project managers don't communicate that downstream. Being able to understand the woes of engineering and the plaints of management simultaneously gives you an advantage to communicate effectively and deliver more efficiently.
- product manager -- Similar to but different than project manager, a product manager sits between the project manager or engineers and the customer or potential customers. The product manager evaluates customer concerns and helps shape the product or products by ensuring that the features you're working on will actually help improve the product's market position. What features are people asking for? What features are people asking for that are negatively impacting the ability of sales to sell the product? What features are people not asking for that they should be? What could make the product better? Those are the questions that the product manager seeks the answers to, and provides those answers to the rest of the team, then puts in a request for the proverbial "Feature X".
Etc., etc. There are positions that benefit from having a developer's mindset that aren't development. By your post here, I can see that you communicate effectively, so you have at least the minimal qualifications necessary that a transition could probably be easily managed.