I think what you're really looking for is meaning. You can be a 'consummate professional' by 'solving challenging problems' in the very best way you can, but it

I think what you're really looking for is meaning. You can be a 'consummate professional' by 'solving challenging problems' in the very best way you can, but it seems like this just doesn't hold much personal meaning for you anymore. I think you can do a couple things to find meaning in your work. First I'd suggest not thinking of your work as 'writing code'. Think of it as 'producing a product', 'helping users', 'facilitating economic and social progress'. Re-gear what you do around those ideas. It reframes what you're doing from just 'mindless mechanical labor' to actually improving someone's life, or enhancing the value of some part of society. If you don't feel like your work is doing that, either change how you do your work, or do some other work. You can focus more on performing the task at hand at the highest level you can. This might involve going back to school, attending conferences/seminar on your subject, compiling lists of inefficiencies with your current work methods, trying to figure out how to work around problems in your current workflows or methods and how to solve them in really beautiful, simple ways. You can look past the task at hand, and look at what it's being used for. What's the end goal? What can you contribute to that has to do with that? It might be a deeper understanding of how someone uses what you create, finding out problems or inefficiencies in those use cases, and working on how to solve those from your position. You can also work on things outside your immediate purview that relate to either the task at hand or ultimate goal. Maybe there's something in the SDLC that's inefficient or creating unnecessary problems. Maybe there's outside groups that have inefficiencies. Maybe there's communication problems, process problems, business problems. What is really involved in the entire value chain of this thing you're working on? How can you contribute, even if it means not working on code? How can you improve the whole process, the whole business? And you can think bigger. How is society impacted by this thing you're working on? What changes could you make at a level outside your organization that would help? Can you get engaged in civil organizations? Can you work directly with communities that have to do with this product? Can you organize a PAC of some sort? Last thing I'd add is to beware a mindset of trying to 'change the world' or 'fix big problems'. I think these are negative perspectives, because they assume the world needs changing, or that things are broken. People that get passionate about an idea often drift toward a more extreme position than is realistic. I've gained a lot more from the perspective of "nothing is or ever will be perfect, but I can try to constantly improve things over time and help people". Often this is just improving tiny little things one at a time, or teaching by example. Cumulatively, it does change the world, but without big expectations, assumptions or implications hung on it.