I'm 20 and will soon be moving to another European country because of circumstances outside my control. To cover rent, food, and other necessities, I'll probably need to work an 8–10 hour shift in a physically demanding or entry-level job.
Before finding out about the move, I planned to keep improving my programming and English so I could eventually apply for developer roles with more confidence. I'm not starting from zero: I've used Python, Django, Flask, REST APIs, SQL, Git, and basic Docker, and I've built projects such as an online store and a job board. However, interview practice exposed gaps in my fundamentals, especially around Python, databases, Django, testing, and backend concepts.
My conversational English is around A2, while my reading and grammar may be closer to B1. I also need to improve my speaking for future interviews with international companies.
My main concern is energy. Physical work has left me exhausted in the past, with no motivation to study afterward. I'm worried that I'll forget what I know, fall behind, or never become ready for a developer position.
For people who have worked tiring jobs while learning programming or another language: how much did you realistically study on workdays? Was 30–40 minutes enough to make progress? Did you study before work, during breaks, or on days off? What balance of theory, exercises, and projects worked best, and how did you avoid burnout and forgetting material? How long did it take before you felt ready to apply for jobs, and what mistakes should I avoid? I'm looking for a sustainable routine rather than an unrealistic four-hour study plan every night.
4 Answers
It’s definitely possible, but consistency matters more than huge study sessions. When I worked a physical job, I aimed for about an hour on normal days and used weekends for longer sessions. On especially exhausting days, I did nothing beyond resting, and that was fine.
A useful progression is to review the fundamentals first, then build one project that forces you to use them. You will forget syntax and framework details; that’s normal. The important skill is understanding the concepts and knowing how to find the information again. Don’t wait until you feel perfectly prepared before applying. Start once you have a couple of solid projects and reasonable fundamentals, then use interviews to identify what to improve.
Be realistic about the job market and avoid measuring yourself against people who can study full-time. A demanding job, relocation, language learning, and programming together may take longer than you expect, and that does not mean you are failing.
Your existing Django, Flask, SQL, Git, and Docker experience is worth developing rather than abandoning. Choose one backend project, make it reliable, add tests, document it, and use interview questions to find the gaps. Apply before you feel completely ready. At the same time, prioritize sleep and recovery; repeatedly studying until two or three in the morning can damage both your health and your learning.
A practical intermediate job with a better schedule can also help. Even support, QA, data entry, or junior technical work may give you useful experience and more energy to continue learning.
I studied while working long shifts and caring for a family, and the routine had to change constantly. Some days I managed an hour or two, while other days I only read for fifteen minutes or did a tiny coding exercise. Those small sessions added up over time.
Use active recall and spaced repetition for fundamentals, but keep building something practical so the theory has a purpose. Once you understand a topic, exercise it until it becomes familiar, then incorporate it into your main project. You don’t need to remember every command forever; professional developers regularly look things up.
Thirty or forty focused minutes can absolutely produce meaningful progress, especially if you finish one small task instead of constantly switching topics. On workdays, revise one concept, solve a couple of problems, or fix one issue in your project. Save larger features and deeper study for days off.
Studying before work often works better than studying after a long shift because your concentration is higher. You can also use commuting or chores for English listening, and add short speaking practice when you have the energy. A simple routine that survives busy weeks is much better than an ambitious schedule that causes burnout.
The biggest problem for me was starting two-hour sessions that I rarely completed. One uninterrupted 25-minute block every day worked better because I didn’t lose the context between sessions.
I also moved into a data-related entry-level role after learning SQL, which helped me get closer to programming. A less exhausting or more technical job can be a valuable intermediate step if one becomes available.