How to Support Your Child Through a Tech Bootcamp
Supporting your child through a coding bootcamp means providing a stable environment, not technical help. Make sure they have reliable internet, a quiet study space, regular meals, and emotional encouragement. The most harmful thing you can do is ask "can you get a job yet?" every week. The most helpful thing is asking "what did you build this week?" and letting them show you.
You Do Not Need to Understand a Single Line of Code
Let me say this clearly: your job as a parent during the bootcamp is not to help with homework. You will not be debugging JavaScript at midnight. You will not be quizzed on what "React" means.
Your job is to provide four things. Reliable internet access. A quiet space where your child can focus for hours at a time. Food on the table. And the belief, even when you do not understand what they are doing, that they are doing something worthwhile.
That last one is the hardest. When your child sits at a laptop for 10 hours and you cannot see any output, it feels like they are wasting time. They are not. They might have spent 6 of those hours fixing a single bug, a tiny error in their code that broke everything. When they finally fix it, the screen looks exactly the same as before. But they just solved a problem that would have stumped them last month. That is growth, even though it is invisible to you.
Do not measure progress by what you can see. Measure it by what they can show you when you ask.
Weeks 1 to 4: The Excitement Phase
The first month feels electric. Everything is new. Your child is writing their first lines of code, building their first webpage, and feeling like a genius every time something works.
They will come to dinner talking about "HTML" and "CSS" and you will nod without understanding. That is fine. Let them talk. They are processing what they learned by explaining it out loud. You are their audience, and that matters more than you think.
During this phase, your child might overcommit. Staying up until 2 AM coding. Skipping meals because they are "in the zone." Let them ride the excitement, but gently remind them that this is a marathon (literally, at McTaba), not a sprint. Sleep matters. Food matters. Burnout at week 3 makes week 8 unbearable.
This is also a good time to set household expectations. If your child is on a full-time track (studying 8+ hours a day), treat it like a job. They should not be expected to run every errand, cook every meal, or entertain visiting relatives during study hours. Talk to the rest of the family about this. A cousin showing up to chat for three hours on a Tuesday afternoon can derail an entire day of learning.
Weeks 6 to 10: The Dip (This Is Where Most People Quit)
Around week 6, something changes. The excitement fades. The concepts get harder. Your child encounters things that do not make sense no matter how many times they read the instructions. They look at other students' work and feel stupid. They start sentences with "Maybe I am not cut out for this."
This is the dip. Every bootcamp student hits it. Every single one.
The dip is not a sign that your child chose wrong. It is a sign that they are learning something genuinely hard. Think about Form Two. Was it not harder than Form One? Did your child not struggle with chemistry or physics the first time? Did they quit school because of it?
What your child needs from you during the dip:
- Do not panic. If they see you panicking about their frustration, they will feel worse. Stay calm.
- Do not compare. "Your cousin's friend finished a coding course in 3 months" is the kind of sentence that makes someone want to throw their laptop out the window.
- Acknowledge the difficulty. "This sounds really hard. I can see you are working at it." That sentence alone can change a bad evening.
- Remind them of progress. "Remember when you could not even make a webpage? Now you are building apps." They cannot see their own progress when they are in the pit. You can.
Most students who survive the dip go on to finish the programme. Most students who quit do so during this exact window. Your calm support during weeks 6 to 10 might be the difference.
Weeks 11 to 20: The Building Phase
If your child makes it through the dip, something shifts. They stop asking "can I do this?" and start asking "how should I do this?" The questions change. The confidence builds. Not overnight, but steadily.
This is when they start building real projects. Not exercises from a textbook. Full applications with logins, databases, payment systems. At McTaba, students build apps with M-Pesa integration during this phase. Your child might ask you to test something on your phone. Say yes. Tap the buttons. Send the test payment. Even if you do not understand what is happening behind the screen, your participation tells them their work matters.
During this phase, your child might become less available socially. Weekend family gatherings might conflict with project deadlines. Saturday study sessions might replace church attendance or family visits. This is temporary. Six months of intense focus is a small price for a career that lasts decades.
If relatives ask why your child is "always on that computer," a simple answer works: "They are in a training programme. They are building software." You do not need to explain what software is. The confidence in your voice matters more than the technical details.
Things That Help vs Things That Hurt
Things that help:
"Show me what you built today." This is the single best question you can ask. It forces your child to articulate what they did, which helps them learn. And it shows them you care about their work, not just the job outcome.
"I made food. Come eat when you are ready." Simple. Practical. Says "I am here" without interrupting.
"I do not understand what you are explaining, but it sounds like you worked hard on it." Honest and supportive. You do not need to pretend you understand JavaScript.
"I believe this will lead somewhere." Sometimes they just need to hear that someone believes in them when they cannot believe in themselves.
Things that hurt:
"Can you get a job with this yet?" Asked once, it is a fair question. Asked every week, it becomes pressure that makes your child feel like they are failing even when they are on track.
"Your cousin is already earning." Comparison kills motivation. Your child is on their own timeline.
"Maybe you should have just gone to university." This sentence, said during a hard week, can undo months of progress. Even if you think it, do not say it while they are in the middle of the programme.
"It has been three months and you still cannot explain what you do." They can explain it. You may not understand the explanation. That is not the same thing.
Practical Things That Make a Real Difference
Beyond emotional support, here are specific, concrete things you can do.
Internet. Coding requires a stable internet connection. If your home Wi-Fi is unreliable, investing in a backup data bundle (Safaricom Home Fibre starts at about KES 2,500/month) is one of the highest-return investments you can make during these 26 weeks. A student who loses connection during a live class or while deploying a project loses hours of work.
Power. Load shedding and power cuts are real. If you do not have a UPS (uninterruptible power supply), your child needs a fully charged laptop battery at all times. Remind them to charge overnight. A power bank for their phone is also useful for mobile hotspot backup.
Space. If possible, give your child a dedicated study area. It does not need to be a home office. A corner of a room with a table and chair, where siblings know not to interrupt during study hours, is enough. Noise-cancelling headphones (even a KES 1,000 pair from Luthuli Avenue) make a big difference in a noisy household.
Schedule protection. Talk to the household about respecting study hours. If your child studies from 8 AM to 5 PM, that is their "work." They should not be pulled away for shopping trips, errands, or lengthy phone calls with relatives during those hours.
Health basics. Sitting at a computer for hours causes back pain, eye strain, and fatigue. Encourage breaks. Encourage water. Encourage stepping outside for fresh air. These sound small, but they prevent the physical burnout that derails many bootcamp students.
The Final Weeks and What Comes After
The last 4 to 6 weeks of a bootcamp are about finishing projects, polishing the portfolio, and preparing for job applications. Your child might be anxious. The end of structured learning means the beginning of job searching, which is its own kind of stress.
During this phase, your child will need your patience more than ever. Job hunting takes time. The first application rarely leads to an interview. The first interview rarely leads to an offer. This is normal in every field, not just tech.
What you can do: resist the urge to set a deadline. "You have one month to find a job or we are trying something else" is panic talking. Some graduates land roles within a month. Others take three to six months. The portfolio and skills do not expire.
Encourage your child to keep building even after the bootcamp ends. Developers who continue working on personal projects, contributing to open-source code, and learning new technologies stay sharp. The ones who stop coding the day after graduation get rusty quickly.
When the job comes, and it will come if your child has real skills and keeps applying, you will look back on these 26 weeks and understand why the struggle mattered. Every frustrating evening, every invisible bug, every "maybe I should quit" moment was building something you could not see at the time: a developer.
Key Takeaways
- ✓You do not need to understand code to support your child. Your job is stability: internet, food, quiet space, and patience.
- ✓Expect a dip around weeks 6 to 10 when imposter syndrome hits. Your child may want to quit. This is normal, not a sign they chose wrong.
- ✓Ask "what did you build this week?" instead of "when will you get a job?" The first question builds confidence. The second destroys it.
- ✓Your child will seem frustrated, withdrawn, or moody at times. Learning to code is mentally exhausting. It does not mean the bootcamp is failing.
- ✓Celebrate small wins. When they show you a button that works on a screen, that button took them hours of effort. Treat it like it matters, because it does.
Frequently Asked Questions
- How can I support my child during a coding bootcamp if I do not understand technology?
- You do not need to understand code. Provide reliable internet, a quiet study space, regular meals, and emotional encouragement. Ask "what did you build this week?" instead of "when will you get a job?" Celebrate small wins and stay calm during frustrating weeks.
- Is it normal for my child to want to quit the bootcamp?
- Yes. Most bootcamp students hit a frustration point around weeks 6 to 10 when concepts get harder. This is called "the dip" and it is a normal part of learning something difficult. Students who push through usually finish strong. Your calm support during this phase matters enormously.
- How long after a bootcamp will my child find a job?
- It varies. Some graduates land roles within a month. Others take three to six months of active job searching. The timeline depends on their portfolio quality, interview skills, and the job market. Continued coding and building projects after graduation keeps skills fresh and improves job prospects.
- What internet speed does my child need for a coding bootcamp?
- A stable connection of at least 5 to 10 Mbps is sufficient for most bootcamps. Safaricom Home Fibre or a reliable mobile data plan works. Stability matters more than raw speed. Frequent disconnections during live classes or while deploying projects cause real problems.
Ready to build real-world apps?
Join the McTaba Labs full-stack marathon (4 months full-time · 6 months part-time). Learn M-Pesa, USSD, and WhatsApp engineering while shipping 8 production apps.
Apply to the McTaba Marathon