I think you have to find what interests you. Think back to the times you were most excited—what was different then? Personally, when it comes to putting code o

I think you have to find what interests you. Think back to the times you were most excited—what was different then? Personally, when it comes to putting code on the screen I am motivated mostly by two things: 1. I am excited to put a puzzle together. The same thing that makes me interested in finishing a basic puzzle like a sudoku applies to writing code. I want to see my end result work, and putting all the steps together in my code is enough to keep me up late. 2. I am oddly excited about learning and applying best practices. Often I initially solve a problem by mimicking existing patterns. Then I will spend hours pouring over man pages and standard library documentation in order to figure out the best way to do something. For me, everything else feeds into those two basic motivations. In my career I get to apply those concepts at a larger scale. I'm finding that my motivations extend to domains other than code, both in my career and in my personal life. I encourage you to reflect and consider the moments when you felt the most joy and the moments when you felt the least joy, and what was different between them.