Learning to code alongside a full-time job is slower but very doable if you plan for limited energy. Budget five to eight hours a week, use mornings or short weekday sessions plus one longer weekend block, follow one track, build projects linked to your current work, and expect roughly a year of steady effort.
What people tell me
I work full time in a job that has nothing to do with software, and I want to move into tech. By the time I get home I am tired, and weekends fill up with family and errands. I start courses with energy and then fall behind after a few weeks. I cannot quit my job because I need the income, and I am starting to think this is impossible for someone in my situation.
A composite of the messages behind this question, with personal details left out.
Key takeaways
- It is possible, but it takes longer. Plan for roughly a year of steady effort, not three months.
- Five to eight focused hours a week, kept for months, beats bursts of twenty that collapse.
- Use your best energy. For many people that is early morning or a lunch break, not late evening.
- Follow one track and one project at a time. Switching costs are huge when time is scarce.
- Your current job is an asset: build tools that solve problems in your own field.
Be honest about the time you have
If you work eight or nine hours a day, plus commute, plus family, you are not going to study four hours a night. People who try usually last two or three weeks. That is not a lack of commitment; it is arithmetic.
What works is a smaller, fixed budget kept for a long time. Five to eight focused hours a week, for twelve months, is 250 to 400 hours. That is enough to learn programming fundamentals, one stack and build a few real projects. It is slower than a full-time learner, but it is real, and you keep your income while doing it.
Find your best hours
Energy matters more than time. An hour when you are fresh is worth two when you are exhausted. Common patterns that work:
| Pattern | Weekday | Weekend | Good for |
|---|---|---|---|
| Early bird | 45 to 60 minutes before work, 4 days | One 2 to 3 hour block | People who are tired in the evening |
| Lunch learner | 30 minutes at lunch, 5 days | One 3 hour block | Office jobs with a proper lunch break |
| Evening, short | 45 minutes after dinner, 3 days | Two 2 hour blocks | People with flexible mornings for family |
| Weekend heavy | 30 minutes reading, 2 days | Two 3 hour blocks | Shift work or unpredictable weekdays |
Pick one pattern and try it for two weeks before judging it. Short weekday sessions are for reading, small exercises and review. Longer weekend blocks are for building.
Pick one track and stay on it
With limited time, switching between Python, JavaScript, data science and cloud courses wastes most of your hours on restarting. Choose one direction, based on what you enjoy and what jobs exist near you or remotely, and follow a structured path. If you are unsure where to start, the Programming foundations roadmap is a good first stage for most paths, followed by a build track like Frontend or Data analytics.
The book How to Learn to Code and Get a Developer Job was written with career changers in mind and is worth reading early.
Use your current job as an advantage
Career changers often think their previous work is wasted. It is not. It gives you domain knowledge and real problems to solve:
- If you work in accounts, build a tool that reconciles two spreadsheets.
- If you work in retail or logistics, build a simple stock or delivery tracker.
- If you teach, build a quiz or attendance app.
- If you work in healthcare admin, build an appointment reminder prototype.
These projects are more interesting to employers than another to-do app, and they give you a strong story: "I understood the problem because I lived it." Data analytics, internal tools and domain-focused products are often natural bridges.
A 12-month outline
| Months | Focus | Output |
|---|---|---|
| 1 to 3 | Programming fundamentals | Small exercises, one tiny command-line or web tool |
| 4 to 6 | One stack in depth | A project related to your current field |
| 7 to 9 | Second, larger project and Git habits | A deployed project with a clear README |
| 10 to 12 | Job search preparation and applications | Resume, LinkedIn, applications and practice |
The last stage overlaps with the free Job search roadmap. Some people also move sideways first, into a tech-adjacent role in their current company, such as analyst or support engineer, which can be a smoother bridge.
Protect the plan from real life
- Set a minimum week. Two hours, even in a terrible week. It keeps the thread.
- Tell your household your study times. It prevents conflicts and gives you accountability.
- Plan exam-like busy seasons in advance. If your job has a peak month, lower your target for that month instead of abandoning the plan.
- Keep a visible tracker. Tick every session on a calendar.
- Stop at a clear next step so the next short session starts without friction.
What a realistic week looks like
Here is an example week for someone following the early bird pattern while working full time:
- Monday, Tuesday, Thursday, Friday mornings: 50 minutes before work. Read one section of the course and do the exercises.
- Wednesday: No study. Family evening.
- Saturday morning: Three hours on the project. Commit and push at the end.
- Sunday: Twenty minutes to review notes and write down the first task for Monday.
That is about six and a half hours. Most weeks will not go perfectly. The goal is to hit the minimum on bad weeks and the full plan on normal ones. After three months, most people are surprised by how far they have come.
Common mistakes
- Starting with a huge plan. Twenty hours a week collapses by week three.
- Buying many courses. One good path finished is worth ten started.
- Studying only on weekends. Long gaps mean relearning. Touch the material a few times a week.
- Quitting your job too early. Keep income until you have evidence, such as interviews or freelance work.
- Going it alone. Find one other learner or a community to share progress with.
For a wider view of switching fields, see Can I get into tech without a computer science degree?.
If you are still stuck
The blog post on moving into tech from a commerce degree covers paths that suit people coming from non-technical work. If you want a plan built around your actual week and job, sign up to Sefism. It is free to learn, new members get credits and the first roadmap is free, and you can ask me directly or book a 1:1 session.
Was this answer helpful?
Read next
Your situation is not quite this one?
Members get written answers to their own questions, a roadmap built for them and feedback on their projects. Early access is open: sign up and your account is active shortly after. Prefer to talk? A free call works too.