I work in an environment that has mainly been "new project" based since I started. There seemed to be an endless well of opportunities to create new software to solve problems and this situation has sustained for the past 5 years where I now have about 10 applications I'm responsible for, written solely by me.
However I fear the well is drying up, as new projects are becoming more infrequent. Of course this was inevitable that after solving so many problems with software, there weren't many problems left to solve. And this creates a new problem, which stems from my inability to communicate other aspects of my value aside from solving new business needs with new software which I, and management ,have grown accustomed to.
Of course everything I've created needs attention, code needs to be refactored, things can be improved, etc. These are project in and of themselves. But knowing the mindset of upper management, I'm afraid not being attached to new opportunities could result in a devaluation of my position. However these fears may be ungrounded, but I need to discover if they're real.
How best to communicate a software engineers value while they're not in the constant "new project" cycle anymore?