Can You Learn to Code While Working a Full Time Job in Nairobi?

Yes, you can learn to code while working full-time. Thousands of Kenyan developers did exactly this. But anyone who tells you it is easy is either selling you something or has never tried it themselves.

The challenge is not that coding is impossibly hard to learn. It is that your time and energy are finite, and a full-time job in Nairobi already takes a big bite out of both. By the time you factor in the commute (often 1 to 3 hours each way), the workday itself, household responsibilities, and basic human needs like eating and sleeping, the remaining hours are slim. And those remaining hours come with depleted energy and willpower.

That said, "slim" is not "zero." Most people have more usable time than they think. The question is whether you are willing to be intentional about how you use it. That means making trade-offs. Some Netflix time becomes coding time. Some social time becomes study time. Some weekend leisure becomes project-building time. Not all of it, but some. For 12 to 18 months, your life gets a bit more focused. The payoff is a career that can dramatically change your financial trajectory.

Let us talk about how to structure this realistically.

Ten hours per week sounds manageable in theory. In practice, finding those hours requires a plan. Here is where most working professionals in Nairobi find their study time.

Early mornings (5:00 to 7:00 AM). This is the single most productive window for most people. Before the workday starts, before the WhatsApp messages arrive, before the household wakes up. Two hours of coding in a quiet house, with fresh mental energy, will teach you more than four hours of distracted evening study. You need to go to bed earlier to make this work, which means restructuring your evenings. It is not glamorous, but it is effective. If you can get 1.5 to 2 hours here, five days a week, that is 7.5 to 10 hours right there.

Lunch breaks (30 to 60 minutes). You do not need to code during lunch. But you can use 30 minutes to read documentation, watch a short tutorial, or review flashcards for concepts you are learning. This keeps the material fresh in your mind between morning and evening sessions. Over a week, these small sessions add up to 2 to 5 hours.

Evenings (8:00 to 10:00 PM). Evenings are the most common study time but also the least reliable. You are tired from work. You might have family responsibilities. Your willpower is at its lowest. If you can get one productive hour in the evening, count it as a win. Do not plan for 3-hour evening sessions and then feel guilty when you cannot sustain them. Use evenings for lighter work: reviewing what you built in the morning, reading articles, or watching tutorials.

Weekends (4 to 6 hours total). Saturday or Sunday mornings are golden. Block out a 2 to 3 hour chunk for project work. This is when you build things: your portfolio projects, practice exercises, side projects. Weekend sessions feel less pressured than weekday ones, and having a longer uninterrupted block lets you tackle bigger problems. Do not sacrifice your entire weekend. You need rest and social time to stay sane. But a focused morning session on one or both days makes a huge difference.

A realistic weekly schedule might look like this: 1.5 hours each weekday morning (7.5 hours), 30-minute lunch reviews three times a week (1.5 hours), and 3 hours on Saturday morning (3 hours). Total: 12 hours. That is enough to make real progress.

Let us address the elephant in the matatu. If you live in Rongai, Kitengela, Ruiru, or Juja and work in the CBD or Westlands, your commute might eat 2 to 4 hours of your day. That is time you could be studying. Here is how to make the commute less of a total loss.

Audio learning on the commute. You cannot code on a matatu (please do not try). But you can listen to podcasts and audio courses that cover programming concepts. Shows like Syntax.fm, JavaScript Jabber, and CodeNewbie explain concepts conversationally. You will not learn to code purely from listening, but you can reinforce concepts, learn about the industry, and stay motivated during time that would otherwise be dead.

Reading on your phone. If you have a seat and your bus or matatu ride is not too bumpy, you can read articles, documentation, or ebook tutorials on your phone. MDN Web Docs, javascript.info, and many coding blogs are mobile-friendly. This is not a substitute for hands-on coding, but it keeps concepts fresh and fills what would otherwise be wasted time.

Reduce the commute if possible. This is easier said than done, but it is worth considering. Can you negotiate one or two work-from-home days with your employer? Many Kenyan companies have become more flexible about remote work since 2020. Even one day without a commute gives you 2 to 4 extra hours for coding. Can you shift your hours to avoid peak traffic? Coming in at 7:00 AM and leaving at 4:00 PM might cut your commute time by 30 to 45 minutes each way. Can you find a co-working space or cafe near your home where you can code before heading to the office?

Consider the commute when choosing a learning format. If your commute is brutal, a self-paced online course might suit you better than one with fixed live class times. You do not want to add more time pressure to an already compressed schedule. Our Tech Foundations course (KES 2,999) is self-paced and designed for people who need to fit learning around a busy schedule.

The most common mistake working professionals make is trying to binge-learn on weekends. They do nothing Monday through Friday, then try to cram 10 hours of coding into Saturday and Sunday. This does not work, and here is why.

Coding builds on previous knowledge. Each concept connects to the last one. If you code on Saturday and then do not touch code again until the following Saturday, you spend the first hour or two just remembering what you were doing. You re-read your notes, re-watch part of a tutorial, and re-familiarize yourself with the project. By the time you are back up to speed, you have lost significant time. Daily practice, even just 45 minutes, keeps everything fresh and eliminates this re-onboarding cost.

Your brain needs time to process. Learning to code is not about memorizing syntax. It is about building mental models for how programs work. Your brain does a lot of this processing while you sleep and during the time between study sessions. Short daily sessions give your brain time to consolidate what you learned before the next session adds more. A 10-hour weekend marathon overwhelms your working memory and much of it does not stick.

Habits are built daily, not weekly. If you code every morning at 5:30 AM, it becomes automatic within a few weeks. You do not have to motivate yourself each time because the routine carries you. A weekly schedule requires you to re-motivate yourself every Saturday, which is much harder to sustain over months.

The target is clear: code something every day, or at least 5 to 6 days a week. Even on your worst, most exhausting day, open your code editor and do 20 minutes. Review a concept. Fix one small bug. Write one function. The act of showing up matters more than the duration. Protect your streak.

Time management advice is everywhere. What people rarely talk about is energy management, which is actually more important when you are learning after a full day of work.

Your brain has peak hours. For most people, cognitive performance peaks in the morning and declines through the afternoon and evening. This is why mornings are better for learning new concepts and solving problems. Evenings are better for review, repetition, and lighter tasks. Trying to learn a complex new topic at 9:00 PM after a long day is fighting your biology. You can do it, but it will take twice as long and retain half as well.

Physical health affects learning speed. This sounds obvious, but it is easy to neglect when you are squeezing study time into an already packed schedule. Sleep is not optional. If you are waking up at 5:00 AM to study, you need to be asleep by 10:00 PM. Cutting sleep to create study time is counterproductive. Your ability to understand and retain new information drops sharply when you are sleep-deprived. Eat properly. Move your body, even if it is just a walk. Dehydration and hunger make it harder to concentrate. Keep water and a snack at your desk when you study.

Mental health matters too. Learning to code while working full-time is a sustained effort over many months. If you burn out, you quit. Build in rest days. Take a full weekend off once a month. See your friends. Do things that are not productive but are enjoyable. The goal is to arrive at month 12 still going, not to sprint and crash at month 3.

Know when to push and when to stop. If you sit down to study and nothing is making sense, your brain might be telling you something. Take a break. Go for a walk. Come back in 30 minutes, or try again tomorrow. Forcing yourself through a wall of confusion when you are exhausted does not teach you anything. It just builds frustration and resentment toward the learning process.

At some point during the journey, you will be tempted to quit your job and go full-time on learning. The math seems simple: more time equals faster progress. But for most people, quitting is the wrong move, and here is why.

Financial pressure is the enemy of learning. The moment you stop earning, every day becomes a countdown. Your savings drain. Your anxiety rises. "Am I learning fast enough?" becomes "Can I afford to keep doing this?" That anxiety makes it harder to concentrate, harder to be patient with yourself, and harder to take the time you need to truly understand concepts rather than rushing through them. Learning under financial pressure is worse in almost every way than learning slowly but steadily while employed.

The job search takes time too. Even after you are job-ready, finding your first developer role typically takes 2 to 4 months of active applications, interviews, and rejections. If you have already burned through your savings during the learning phase, those months of job searching become terrifying. Having a salary during the job search means you can be selective about which offer you accept rather than grabbing the first thing that comes along.

Part-time study takes longer but has a higher completion rate. People who quit their jobs to learn full-time often set aggressive timelines ("I will be job-ready in 3 months"). When they miss that timeline, which is common, the pressure mounts and many give up entirely. Part-time learners set more realistic expectations and are more likely to actually finish because they never reach a crisis point.

The exception. If you have 6+ months of living expenses saved, no dependents, and a high tolerance for uncertainty, full-time study can work. A structured bootcamp like the McTaba Labs marathon (26 weeks, KES 100,000) gives you a clear timeline and accountability. But this is the exception, not the default advice. For most working professionals in Nairobi, the part-time path is smarter.

If you have read this far and you are thinking "I want to try this," here is exactly what to do in the next seven days. No big commitments. Just a test run.

Monday evening: Set your alarm 90 minutes earlier than usual for Tuesday. Prepare your laptop, charger, and a glass of water the night before. Create a free McTaba Academy account so the platform is ready when you sit down.

Tuesday to Friday mornings: Wake up at your new alarm time. Spend 60 to 90 minutes working through introductory HTML and CSS. Do not watch videos longer than 15 minutes without actually typing code yourself. The goal is hands-on practice, not passive consumption. If you are stuck, write down your question and move on. You can research it during your lunch break.

Saturday morning: Block out 2 to 3 hours. Build something small: a personal webpage, a simple landing page, a recipe page. It does not matter what. The goal is to create something from scratch using what you learned during the week. This is where learning solidifies.

Sunday: Rest. Review what you built. Think about whether you enjoyed the process. Did the mornings feel sustainable? Were you able to concentrate? Did the commute give you any useful review time?

After one week, you will have real data about whether this schedule works for your life. You will know if mornings suit you. You will know if the subject interests you. You will know if you can sustain the discipline. That is infinitely more useful than reading articles and wondering. The only way to find out is to try.