I'm 43 and have been coding in some capacity for nearly 30 years now. I've had a few times where I got tired of coding and usually what I realized is that the t

I'm 43 and have been coding in some capacity for nearly 30 years now. I've had a few times where I got tired of coding and usually what I realized is that the type of coding I did at work wasn't that interesting, or else the work itself consisted too much of some big-co. bureaucratic nonsense that made it not fun. In those moments is usually when I start playing around with side projects. I'd recommend starting up a low pressure project on the side. Figure out what made coding fun for you and focus on that in your project. It can be hard to get started, so you want to make sure it's fun and not full of too much boring stuff. What I mean by the latter is that there are certain aspects of coding that you do for work that are necessarily boring, at least for me. For instance, writing unit tests, or making clean commits, etc. I used to find those elements fun in my side projects but over time I realized that I "learned" them enough and that doing them made the side projects less fun. Instead, I now throw caution to the wind when doing stuff on the side. If something isn't interesting, I don't do it, or I try to limit the amount of boring stuff. It helps to have low expectations and just engage in things for fun. Over time, you can really build up something nice if you work on it consistently. Just don't focus on the end goal too much or how much you're progressing because that's when it starts feeling like "work".