I've been programming since I was 14, starting with simple chat bots and gradually exploring web and mobile development, C, assembly, low-level architecture, servers, security, Raspberry Pi projects, and more. Now I'm 19 and about to begin a five-year work-and-university IT program, so I'm grateful that my hobby is becoming my career.
Lately, though, I've been feeling strangely empty and mentally blocked. I used to code for four to eight hours a day and still feel motivated, but recently I've been staring at my projects for hours, changing a few lines, and then losing track of what to do next. I enjoy my projects and don't want to abandon them, but I'm worried that this lack of energy means I'm falling behind.
I also feel a lot of pressure to succeed financially and eventually give back to my parents. Technology changes quickly, and at only 19 I already feel as though I'm running out of time to build a successful future. I know taking a break may be the obvious advice, but I'm afraid that slowing down will make me miss important opportunities.
Has anyone with more experience dealt with this kind of emptiness, burnout, or fear about the future? How did you learn to pace yourself and stay motivated without giving up on programming?
4 Answers
Take a breath—you don’t need to know everything to become a good developer. Technology changes quickly, but there will continue to be opportunities for people who are curious, capable, and willing to keep learning. Spending every waking hour at a computer can drain the passion out of something you genuinely enjoy.
You’re about to start both university and a job, which will demand a lot of energy. Being awake at 3 AM staring at a project is a sign that you should slow down before starting that next chapter already exhausted. Give yourself room to rest and do things that have nothing to do with programming. You’re not falling behind by taking care of yourself.
Programming is only one part of being a professional engineer. A lot of the job involves clarifying what clients actually need, reviewing designs, setting realistic expectations, planning architecture, mentoring teammates, and preventing bad code from becoming a bigger problem.
Your ability to pace yourself is part of your career skill set. If you turn a hobby into nonstop work, it can become tiring and routine, but you can often bring the enjoyment back through a new topic or project. Set boundaries around work, take real time away from screens, and develop hobbies that let your mind recover.
As for AI and the future, it can produce impressive results, but using it does not replace understanding. Inexperienced developers can generate complicated or incorrect solutions very quickly. Your broad foundation and ability to reason are valuable, but they’ll be much harder to demonstrate if you burn yourself out. Learning how to rest and manage your limits will help your future more than squeezing another few hours out of an exhausted brain.
This sounds like more than ordinary loss of motivation and could be burnout, depression, or both. Consider speaking with a doctor, counselor, or mental-health service through your university. You don’t have to diagnose yourself or wait until things become severe before asking for help.
Don’t rush yourself. I moved away from programming as a teenager and spent about a decade feeling like I had ruined my chances. When I returned around 30, a surprising amount came back quickly. I’m now finishing an associate degree, working in an IT-related role, and have strong references and a promising software offer.
You’re only 19. A slower period now won’t determine your entire career, and even a long break doesn’t necessarily erase what you’ve learned.
That’s genuinely encouraging. It helps a lot to hear from someone who stepped away and still managed to build a good career later.
That’s reassuring to hear, especially from someone with substantial experience and a successful project. I think I needed someone to remind me that things are probably going to be okay.