I'm 21, living alone in Australia, and working full time in a restaurant. University wasn't affordable, so I've been teaching myself programming. I started with web development in April 2024, worked through HTML, CSS, JavaScript, TypeScript, and related topics, and eventually reached Next.js. I also studied data structures and algorithms for a while.
As my projects became more complicated, I struggled to build things without tutorials or AI and started losing track of how the code worked. Around late 2024 and early 2025, my mental health declined badly, eventually leading to a breakdown and depression. Coding had been something I loved, but I became unable to do it and was prescribed antidepressants for a time.
Now I'm slowly recovering and trying to return to programming, but I feel like I've forgotten basic concepts and terminology. When I look something up, I sometimes recognize it and remember that I used to know it, but the process is painful and discouraging. I'm also distracted by thoughts of learning animation or creating content, even though I don't feel ready to share anything yet.
How should I approach restarting without overwhelming myself? Has anyone rebuilt their skills and motivation after a similar period of depression or burnout?
4 Answers
Don’t assume you need to start from zero. Memory often comes back when you encounter the concepts again, even if you can’t recall them immediately. Review the fundamentals at a comfortable pace—HTML, CSS, JavaScript, then TypeScript—and make small projects rather than trying to jump straight back into a large framework. Looking things up is normal, even for experienced developers.
You may benefit from temporarily changing the activity instead of forcing more web development. A short experiment with Blender, animation, or another technical creative tool could restore some curiosity and give you a break from the stack that became associated with burnout. After a week or two, you can decide whether you want to return to coding. The goal should be enjoyment and recovery first, not maximum learning efficiency.
Choose a small project you genuinely want to see finished, then break it into very simple phases. Write down what each feature should do before coding, experiment with the code, and change one thing at a time so you can observe the result. Tutorials and AI are fine as long as you pause to explain the code to yourself and rebuild parts of it without blindly copying.
A useful technique is to make your reasoning visible. Before writing code, describe the goal in plain language, write a rough plan or pseudocode, and add checks or assertions for what you expect each part to do. You can even work through a small example on paper. This reduces the feeling that the program is a mystery and makes it easier to find where your understanding breaks down.
That makes sense. I think I’ve been treating every forgotten detail as proof that I’m failing instead of accepting that reviewing and searching are part of the process.