Can You Work While Attending a Coding Bootcamp in Kenya?

You can work full-time and attend a coding bootcamp. Thousands of people do it. But anyone who tells you it is easy is lying. For 26 weeks, you will code in the evenings after a full workday. You will spend Saturdays building projects instead of resting. Sundays become study days. Drinks with friends, weekend getaways, and long Netflix sessions get replaced by debugging sessions and documentation reading.

That is the trade-off. Not impossible. Not comfortable. If you go in expecting it to be effortless, you will quit by week 4. If you go in knowing it will be hard but temporary, you can get through it.

The financial logic is clear though. If you make KES 40,000 a month and quit for 4 months to attend a full-time bootcamp, you lose KES 160,000 in income on top of the tuition. A part-time program that costs KES 120,000 but lets you keep your salary is actually much cheaper in total cost.

Not all bootcamps are built for working professionals. The format matters.

Full-time bootcamps run during working hours, typically 9am to 5pm or similar. They expect 40 to 60 hours per week. You cannot attend one while holding a regular job. Some people take leave, quit, or negotiate a sabbatical. This is realistic only if you have savings to cover your expenses for the full program duration, or someone else is covering your bills.

Part-time bootcamps run evenings and weekends. They expect 15 to 20 hours per week. Sessions might be 7pm to 9pm on weekday evenings and 4 to 6 hours on Saturday. McTaba Labs' 26-week marathon is structured this way. The program takes longer (26 weeks instead of 12 to 16), but you keep your income.

If you are currently employed and cannot afford months without income, a part-time program is your only realistic option. Do not try to attend a full-time bootcamp while working. You will burn out within weeks and waste both the tuition and the opportunity.

Here is a realistic weekly schedule for someone working a 9-to-5 job and attending a part-time bootcamp.

Monday to Thursday: Work 8am to 5pm. Rest and eat from 5pm to 7pm. Code from 7pm to 9:30pm. That is 2 to 2.5 hours of coding per evening, totaling 8 to 10 hours across the work week.

Friday: Work until 5pm. Most people take Friday evening off. Your brain needs it. If you can squeeze in an hour, great. If not, do not feel guilty.

Saturday: This is your main study day. 4 to 6 hours of focused work. Morning is usually better because your energy is higher. Projects, exercises, catching up on anything you missed during the week.

Sunday: 2 to 3 hours for review, reading documentation, or light practice. Save Sunday afternoon for rest. Burnout is your biggest enemy over 26 weeks, not the difficulty of the code.

Total: 15 to 20 hours per week. Some weeks you will hit 20. Some weeks life gets in the way and you manage 10. That is normal. The key is consistency over months, not perfection every week.

The challenge of working and studying is not finding the hours. Twenty hours per week exists in everyone's schedule. The challenge is having the mental energy to actually learn during those hours.

Coding after 8 hours of work is different from coding fresh in the morning. Your brain is tired. Your attention span is shorter. You make more mistakes. You get frustrated faster. This is normal, not a sign that you are not cut out for coding.

Some practical things that help. Eat before you code. Coding hungry is miserable and unproductive. Keep water at your desk. Take a 5-minute break every 45 minutes. Use your commute (if you have one) to listen to tech podcasts or review concepts mentally. Do not try to learn difficult new concepts after 9pm. Use late evenings for practice and review, not new material.

Exercise matters more than you think. A 20-minute walk before your evening coding session clears your head and resets your focus. People who maintain some form of physical activity during a bootcamp consistently report better focus and less burnout than those who cut it entirely.

This depends on your relationship with your employer and your industry.

If your employer supports professional development, tell them. Some companies offer study leave, flexible hours, or even partial tuition support for skills training. At minimum, they may let you leave 30 minutes early on session days or shift your working hours slightly. You do not know unless you ask.

If your employer would view learning to code as a sign you are planning to leave, use your judgment. You are not obligated to disclose personal education plans. But be aware that your energy levels and availability may change noticeably during the program. Colleagues will notice if you are more tired than usual or declining every after-work event for 6 months.

If you work in tech already and are upskilling, this is usually a straightforward conversation. Most tech companies actively encourage learning. If you are in a completely different industry and learning to code as a career exit strategy, discretion might be wiser.

People who combine work and bootcamp do not usually quit because the material is too hard. They quit because of accumulated exhaustion. The breaking points follow a pattern.

Week 3 to 4: The novelty wears off. The initial excitement is gone and the grind begins. Every session feels like effort rather than exploration. This is when the first wave of dropouts happens.

Week 8 to 10: The material gets harder. You are past the basics and into real complexity. Combined with two months of reduced sleep and no weekends, this is the toughest stretch. If you get through this, you will probably finish.

Any week with a life event: A family emergency, a work crisis, getting sick, or any disruption that forces you to miss a week or two. Catching up after falling behind while still working full-time feels overwhelming. This is where good communication with your instructors matters. Tell them early. Get a plan. Do not just vanish.

Knowing these danger points exist helps you prepare for them. When week 4 feels grim, you can remind yourself that it is a known pattern, not a personal failure.

1. Prep your meals on Sunday. Cooking every evening eats into coding time.

2. Set up your coding environment the night before. Do not waste 20 minutes of a 2-hour session fiddling with settings.

3. Tell your partner, family, or housemates your schedule. "I code from 7 to 9:30 on weeknights" sets boundaries.

4. Find one study partner from your cohort. Accountability doubles when someone else is counting on you.

5. Do not skip two consecutive days. One day off is rest. Two days off becomes a habit of not coding.

6. Use dead time. Commute on a matatu? Read documentation on your phone. Waiting at a bank? Review yesterday's code mentally.

7. Reduce social media during the program. Not eliminate, just reduce. Those 45 minutes of scrolling are a coding session.

8. Sleep enough. Cutting sleep below 6 hours to code more is a false economy. Tired coding is bad coding, and it leads to burnout.

9. Take one full day off per month. No coding, no thinking about coding. Your brain needs genuine rest to consolidate what you have learned.

10. Celebrate small wins. Deployed your first app? Passed a tough exercise? Finished a project? Acknowledge it. The marathon is long and milestones keep you going.

11. When you are stuck, step away for 15 minutes. The answer often appears after a break, not after an hour of frustrated staring.

12. Remember why you started. Write your reason down during week 1. Read it during week 8 when you want to quit.