[twobyfour]

15 hours a day? You're almost certainly burnt out. Can you take 6-8 weeks off work? See what happens if you force yourself to step away from the keyboard for that long.

That will also give you a chance to re-evaluate why you code. Mastering a skill can be a motivating challenge. But if that's your motivation for leaning it, you'll run out of steam once you reach a level of mastery that satisfies you.

It could be that you need a new skill to master. Perhaps something technical (math? Machine learning?) Perhaps something non-technical (finance? People management? Carpentry?)

It could be that you simply need a goal or challenge to which you can apply your skills. For many of us, programming for programming's sake gets old pretty quickly. But building something that solves a problem for people doesn't. Maybe the problem you'll solve is something small (the Jetsons promised me a robot that will unload my dishwasher...) or maybe it'll be big (climate change? Refugee crises? World peace?).

Or you might be one of us who doesn't have an explicit purpose to their life except to muddle through and spend time with the people we love. There is absolutely nothing wrong with that. It just requires accepting that programming doesn't have to be an all-consuming passion. If it's something you just do for 30-50 hours per week in order to earn a paycheck, that's ok too. If you'd rather spend your 40 hours doing that than doing sales, that's really all that matters. Find your meaning and challenge in your loved ones and your hobbies.