Lost my appetite for software development, any recommendations?

Thanks for sharing, and it's quite refreshing to hear your situation because.. you are not alone. I often feel that way.. dead end jobs, useless projects, lost of energy, lost of ambitions, I can go on all day. My remedy to this is just to realize that this is a wave, a phase in which you're at the bottom of that wave, a sort of "life recession" where you get forced to question a few things. Ten years ago, I was so fed up of foking programming that I never thought I'd get the buzz back. Today, I'm still buried in projects, but my outlook changed somehow, I find this interesting again. It's funny, because it kind of coincided with my kids outgrowing the diaper years :)

I think this is possibly partially burnout, it could also be part of "growing up", or perhaps you shifted priorities. I used to work 50-60 or even 80 hours a week, people praised me that I would respond within minutes on a Sunday evening - and I would be proud of it, too.

But that was 10 years ago. Now I don't have work email on my phone, I work freelance, so I get to decide on what I want to do next; and work in general just doesn't take up that high a priority anymore (being a freelance contractor has helped me develop this trait of "I'm here to do work for your company, and you pay me").

I enjoy working on side projects and learning new stuff, and one side project I started 8 years ago is still profitable to this day, but I wouldn't have started it anymore today, the motivation and naivite just don't exist anymore, plus since I have a family to support, it would be too risky to start that big of a side project.

Maybe it's time to just take a step back and assess what your long term goals are and in general what you want to achieve in life.

And it also reminded me of this: http://www.paulgraham.com/kids.html

"I hate to say this, because being ambitious has always been a part of my identity, but having kids may make one less ambitious. It hurts to see that sentence written down. I squirm to avoid it. But if there weren't something real there, why would I squirm? The fact is, once you have kids, you're probably going to care more about them than you do about yourself. And attention is a zero-sum game. Only one idea at a time can be the top idea in your mind. Once you have kids, it will often be your kids, and that means it will less often be some project you're working on."

Talk to your manager and see how they think you are doing. You might be too hard on yourself and/or in awe of co-workers.

It sounds like you are in a good spot to soak up knowledge from people that are highly respected in their fields. Try to understand what these improvements and new solutions offer to the product. It is possible that the eager devs are just spinning their wheels and/or reinventing wheels because of new shiny libraries. If they truly are very advanced in their fields, I can't imagine your manager has the same expectations of you and them. Maybe your role is to bang out awesome work that helps them keep their brains engaged in the very advanced work they do (you didn't describe what it was but it sounds more than CRUD apps).

Another approach is to recognize you are a professional and that there are times where you simply aren't motivated. I'm sure this happens in other professions. There are days/weeks I just am bored doing what we do. Software development of business applications just isn't terribly exciting. Figuring out problems and creating things in code is fun though. Think about what brought you into software development, maybe there is an ember still there you can slowly get burning again.

Family and maturity change your perspective. While younger developers are chasing the next "shiny new thing", you just want to put your time in and go home. That's nothing to be ashamed of. To satisfy "getting home faster", I suggest you concentrate your effort and attention on improving the development process. What rote work or common functionality can you make easier to build/deploy? Ask yourself what the last coding project that you were enthusiastic about was and try to work on something similar. Or, pick something completely different so that the process of learning reminds of why you used to think coding was worthwhile.

Yes, it has happened to me. For some reason, I totally lost interest and people who knew me were surprised I moved away from technology.

This phase is generally difficult to deal with. Somehow we have a strong identity with our career and leaving that feels bad for whatever reason. And when people are surprised, it almost makes you feel guilty. But when I got over that I realised if we take these temporary emotions out of equation it makes sense to move on and start over. Our analytical mind would always come handy in whatever we do.

In my case what helped me was while I was clear I lost interest in technology I had to do some soul searching to find out on what I wanted to do instead. This took some time for me to figure out. And some more time to figure out on how to monetise it. But the effort is worth it.

But I think it would be difficult for anybody to tell you what direction you need to take. It depends on what actually you want to do.It could be managing, consulting on domain, freelancing, taking up a different route, anything else you always liked but were not thinking as a career choice.It also depends on the compromises you can make.

Some deep introspection helps. Maybe this phase goes away as well. Give it sometime and watch what you think about often. That might give a clue. If it is a new journey, talk to people who have done that, chart out a plan before taking a plunge. All the best.

They say coding is a young man's game for a reason - many, many people burn out after 5-10 years. Normally when they do, they either plod along at decreased speed or move into business and managerial roles.

Career wise, it comes down to 2 things: Your own expectations of how you are doing AND your manager/team's expectations of how you are doing. It seems like you are struggling with your own expectations of how you THINK you should be doing. I suggest you look at how your team thinks you are doing. If they are happy with you, that's great. You definitely want that first.

Maybe look for related tasks that no one else wants to do? I enjoy polishing, hardening, fixing, and optimizing existing code. Turns out a lot of "great" programmers can't be bothered to check error statuses, document their stuff, handle unusual cases, etc.

Just an idea. But yeah, can relate.

it sounds like you could be a really good manager because you wouldn't assign stupid tasks that don't really need to be done

Check biohacking or biofabrication.