Why Most People Quit Coding Bootcamps in Kenya, and How to Not Be One

Bootcamp marketing is full of success stories. Someone who was selling mitumba six months ago is now a junior developer earning KES 80,000. A single mother who learned to code at night just shipped her first freelance project. These stories are real. But they are the survivors, and survival rates in bootcamps are not great.

Nobody publishes official dropout numbers in the Kenyan market. There is no regulatory body tracking completion rates. But if you talk to bootcamp operators honestly (and we do, because we are one), the patterns are consistent. A significant portion of students who enroll never finish. Some stop showing up after the first month. Others hang on for weeks, falling further behind, before quietly disappearing.

This is not because Kenyan learners are less capable. It is because the conditions that cause dropout are baked into the experience, and most students walk in without knowing what to watch for. If you understand why people quit, you can plan around each failure mode before it hits you.

This is the biggest one, and it starts before day one. Bootcamp marketing sells a story: you will learn to code, it will be challenging but exciting, and in a few months you will emerge as a developer. That story is technically true, but it leaves out the emotional reality of the process.

Here is what the experience actually feels like for most people. Week one is exciting. Everything is new, you are building your first HTML page, the community is buzzing. Week two is still okay. You are learning CSS, things look like a real website, you feel capable. Week three is where it shifts. JavaScript starts. Suddenly the concepts are abstract. You cannot see what you are building. The code does something you did not expect, or it does nothing at all, and you have no idea why. The confidence you built in weeks one and two evaporates.

By week four or five, you are deep into territory where nothing makes sense on the first read. You look at other students who seem to get it faster and assume something is wrong with you. You start missing sessions or assignments. Not because you are lazy, but because sitting down to study something that makes you feel stupid requires a kind of emotional energy that nobody warned you about.

The fix is not to lower the bar. The fix is to know this is coming. Every learner we have ever seen goes through a period where coding feels impossible. It is not a sign that you are failing. It is the normal shape of the learning curve. If you walk in expecting that dip, you are far more likely to walk through it instead of walking away.

A full-time, 12-week, in-person bootcamp is great if you have no job, no family obligations, and savings to cover three months of zero income. For most people in Kenya, that description fits almost nobody. Yet many bootcamps market their full-time programmes as the gold standard, and students sign up hoping they can "make it work."

Making it work usually means waking up at 5am to study before going to your job, or staying up until midnight after putting children to bed, or skipping family events and social commitments for weeks on end. That is not sustainable. The human body and mind need rest. The people who burn themselves out trying to maintain an impossible schedule do not quit because they are weak. They quit because the format was wrong.

On the other end, fully self-paced programmes fail for different reasons. Without fixed deadlines, assignments pile up. Without a cohort moving at the same speed, there is no social accountability. You tell yourself you will catch up next week, and next week becomes next month, and eventually you stop logging in.

The format that works for most working adults is somewhere in between. Fixed milestones with some flexibility in when you meet them. A cohort that creates social pressure without requiring you to match someone else's schedule hour by hour. Enough structure that you cannot ghost without someone noticing, but not so rigid that missing one session puts you permanently behind. Before you enroll anywhere, ask yourself honestly: does this schedule fit the life I actually live, not the life I wish I lived?

Learning to code alone is possible. But learning to code alone while also dealing with self-doubt, confusion, frustration, and the temptation to quit is a different challenge entirely. Most bootcamps provide some level of community, a Slack channel, a WhatsApp group, maybe office hours with an instructor. The problem is that most students do not use these resources, especially when they need them most.

There is a painful irony here. The moment you most need to ask for help is the moment you feel most embarrassed to ask. You have been stuck on a bug for three hours. Everyone else seems to understand the concept. You do not want to post your question because it might seem too basic. So you sit alone with your frustration, and the frustration compounds until quitting feels like relief.

The people who finish bootcamps are not the ones who never get stuck. They are the ones who get stuck and reach out. They post the "I do not understand any of this" message. They show up to office hours even when they feel behind. They find one other student who is at a similar level and text each other daily, even if it is just "I did 30 minutes today."

If you are considering a bootcamp, think carefully about what support looks like for you. Not in the abstract, but practically. When you are frustrated at 9pm and want to quit, who will you contact? If the answer is "nobody," that is a problem you need to solve before you start. Find a study partner. Tell a friend or family member what you are doing so they can ask you about it. Join a community where asking basic questions is genuinely welcomed, not tolerated. That safety net is not optional. It is part of the infrastructure of finishing.

Your landlord raises the rent and you need to pick up extra work. A family member gets sick and you spend two weeks at the hospital. Your employer changes your shift and your study schedule collapses. Your phone breaks and you cannot access materials for a week. These are not hypothetical scenarios. They are the normal texture of life in Kenya, and they hit right in the middle of your bootcamp.

The problem is not that life interrupts. The problem is that most bootcamps have no real recovery mechanism. If you miss two weeks, you are two weeks behind, and the curriculum keeps moving. The gap between where you are and where the class is grows wider every day. Eventually the gap feels unclosable and you stop trying.

Before you start any programme, ask the administrators directly: what happens if I need to pause for two weeks? Can I join the next cohort without paying again? Is there a way to catch up that does not require doubling my study hours? If the answer is "just watch the recordings," that is not a recovery plan. That is a brush-off. A real recovery plan involves human check-ins, adjusted milestones, and acknowledgment that pausing is not the same as quitting.

On your side, the best defence is a buffer. Do not start a bootcamp during the busiest season at your job. Do not start if you know a major life event is coming in the next month. And build some slack into your schedule from the beginning. If the programme expects 15 hours a week, plan for 20. That way, when you inevitably lose a few hours to life, you are behind your own schedule, not behind the programme's.

This one is tricky because it goes both ways. Some bootcamps try to cram so much into a short timeline that students never get a chance to absorb anything. You learn HTML on Monday, CSS on Wednesday, JavaScript on Friday, and React the following week. Each topic is introduced before the previous one has settled, and you end up with a shallow understanding of everything and a deep understanding of nothing.

Other programmes go so slowly that more experienced learners get bored, disengage, and drift away. If you have already built a few websites on your own and the first month is spent on HTML basics, you lose momentum. By the time the curriculum reaches material that challenges you, you have already checked out mentally.

The fix is partly on the bootcamp (good programmes assess your starting level and adjust), but mostly on you. Before you enroll, look at the full curriculum timeline. Be honest about your current level. If you have never written a line of code, a 12-week programme that covers full-stack development is probably going too fast for real learning. If you have been coding casually for a year, a programme that spends four weeks on the basics will bore you.

The right programme meets you roughly where you are and pushes you just past your comfort zone consistently. Not so far that you feel lost every day, not so gently that you stop growing. If you cannot tell from the syllabus whether the pace is right, ask to talk to a recent graduate whose background is similar to yours. Their experience will tell you more than any marketing page.

Here is the practical version of everything above, distilled into actions you can take before and during a bootcamp.

Before you start: Set your expectations honestly. You will have weeks where you hate it. That is normal, not a sign you should quit. Tell at least two people in your life that you are doing this, so someone notices if you disappear. Check that the schedule fits your actual life, including the bad weeks. Ask the programme what happens if you fall behind or need to pause.

Weeks 1 to 2: Use the easy period to build habits, not just skills. Decide on a fixed daily study time and protect it. Find your study partner or accountability buddy. Learn how to ask questions in the community channel so it feels natural before you desperately need it.

Weeks 3 to 6 (the danger zone): This is when most people quit. Expect confusion. Expect frustration. Expect days where you sit down and feel like you learned nothing. Keep showing up. The goal during this period is not to understand everything perfectly. It is to not quit. Understanding comes later, sometimes weeks later, when something suddenly clicks because you have been building a foundation you could not see.

After the danger zone: If you make it through weeks 3 to 6, something shifts. The foundational concepts start connecting. You build something small but real and it works. The frustration does not disappear, but it changes character. It stops feeling like evidence that you cannot do this and starts feeling like a normal part of the work. That is the turning point, and most people who reach it go on to finish.

The McTaba Full-Stack AI programme is designed around these patterns. The cohort structure creates accountability. Mentors check in when you go quiet. The pace builds gradually instead of dumping everything in week one. But regardless of which programme you choose, the survival playbook is the same: set honest expectations, build a support system, plan for the hard weeks, and keep showing up.