← B-Sides

Only the pull needs internet

How I'm designing a web development course for one student: a founder in The Gambia with a Windows laptop, costly internet and 5 to 7 hours a week.

In September, a post turned up in my r/learnprogramming feed: “How do I build a simple exam questions website from scratch with zero coding experience?”

I’m from The Gambia. Students here who need WAEC past exam papers either buy printed booklets from the market or they go without. There’s nothing clean and organized online. I want to build that.

The author was Saikou Jabbie. He had never written a line of code, but he already had a better product spec than some I’ve been handed at work: “You pick a subject, a year, and a paper. It shows you the questions. You can click to see the answers. That’s it.” I offered to help him build it.

A few weeks in, he told me what he actually wanted. He didn’t want to run a site somebody else had coded. He wanted to write the code himself, and to become a developer. So alongside the site, I’m building him a course.

I’ve spent five years teaching cohorts. This course has one student, and every decision in it starts from what I know about him.

The brief

Before writing a lesson, I sent Saikou five questions on WhatsApp. He answered the same day:

  • He has a Windows laptop and prefers it to his phone.
  • Internet is expensive and unreliable, but within reach.
  • He has 5 to 7 hours a week, in his final year of college. Sometimes a whole day, “if I’m motivated/enjoying it”.
  • He wants to become a developer.

A week later he added something I hadn’t asked: reading is a struggle for him. He grew up on games and films, not books, and never got used to it. That changed the most. Lessons stay as short as they can, and further reading is optional, two or three links at the end.

a bootcamp intake form would file these under barriers. here they’re the spec

Git on day one

Most beginner courses get to Git a few weeks in, as a way to save work. In Saikou’s course it comes first, because Git is how the course reaches him.

Everything lives in one repo on his GitHub account. I write lessons in lessons/. He writes his exercises in work/, plus a few lines in journal.md after each session. We never write in the same folder, so a pull never runs into a merge conflict.

A study session goes like this. He runs git pull to get any new lessons, then reads and works offline, committing as he goes. He pushes when he has a connection, and if he doesn’t, the commits wait on his laptop until next time. The pull is the only step that needs internet before he can start.

Everything else that costs data happened once, in Lesson 0.2: VS Code, Git, Python, Node.js and pnpm, which keeps one shared copy of each package so nothing downloads twice. Further reading links go to text pages, never video.

The repo works for me too. I can’t sit next to him, so his commit history is how I watch him work.

Write ahead, release one at a time

I write a lesson or two ahead and keep them on my machine. When Saikou tells me he’s finished one, I read his commits and his journal, then write the next lesson’s second step: feedback on the lesson he just did, using his own code.

That’s why the next lesson waits for him. In Lesson 0.7 he added WASSCE grades, A1 to F9, to a program that turns a mark into a percentage. He wrote his own message for each grade, and he wrote them as loot rarities: an A1 is “epic”, a B2 “legendary”, a C5 “common”. But his conditions skipped the boundaries, so a mark of 74% got no grade at all. Lesson 0.8 opened with that bug, and he fixed it before starting anything new.

He’s come around to the routine. From his journal after Lesson 0.8: “I’m liking it now because it’s like a revision, and I need, cause I low-key forget everything after a lesson.”

Sometimes a fix can’t wait for the next lesson. His Lesson 0.8 guessing game got stuck in loops that never changed the guess. He committed it anyway, with the message “add broken guess.py file”, which is more honest than most commit messages I’ve reviewed. So I held Lesson 0.9 back and pushed a feedback file on its own, with no checklist and no time limit.

His clock, not mine

Lesson 0.4 said “About 1 hour” at the top. His commits showed it took him an hour and a half to two hours. Lessons 0.6 and 0.7 came out the same way.

So from Lesson 0.8, each lesson’s header gives a range at his pace instead of a single figure at mine: “About 2–4 hours” rather than “About 1½ hours”. Any lesson whose range runs past four hours gets split. Each lesson still fits in one sitting, so a busy week costs him a lesson, not his place.

Try first, with a net

There are no answer keys in the repo. When he’s stuck, I give him a hint before an answer, the same “try first, then ask” order I wrote about in Working code isn’t the goal.

There’s one exception. When a later step in a lesson builds on code he’s asked to write, the lesson includes one way to write it, collapsed under “Stuck? Show one way to write it”, after the hints. He still tries first. But when every question goes over WhatsApp and he might not have signal, one stuck moment can cost him the rest of the session.

The pattern is borrowed from research on faded worked examples: a fully worked example, then a step with partial support, then a problem with none.1 The exercises at the end of each lesson stay answer-free.

Make it his

By Lesson 0.6, the lessons were accurate and colorless, and I could tell. So from then on, every lesson has at least one exercise that’s his. In hello.py he wrote three facts about himself. In 0.7 he built a boss fight for a roguelike, which his journal says he “enjoyed a lot”. The next lesson has him rank his own top 5 and let random.choice pick one.

I know what his top 5 films are, because I asked. Into the Spider-Verse is first.

it’s on my list too. so is God of War. he’s played all eight console games. I’ve played two

“Like high school Trig”

The most useful line he’s written so far is from the same journal entry as the broken guessing game:

My problem is that, I don’t actually understand their meaning, I have to keep trying until I get what I want. It’s kinda like high school Trig, I never fully understood those functions but I knew how to use them. But this isn’t high school, I don’t want to forget anything I’m learning.

He was talking about loops. Plenty of students feel this way and never say so. If he hadn’t written it down, I’d have kept reading his working code as understanding.

Lesson 0.8 had already tried to give him that meaning. It compared a while loop to a bouncer at a club. The condition is the bouncer checking your ID, and if it passes, you’re let into the block. With if, the bouncer checks you once. With while, every time you finish the block you’re back outside at the door, and the bouncer checks you again. If nothing about you changes, you get in every time, forever.

His guessing game was that bouncer. The guess never changed inside the loop, so the bouncer waved it back in every time.

The lesson ended that section with a question: what changes inside the loop, so the condition can become False? He’d read it, and it hadn’t stuck yet. So the feedback file didn’t try a new explanation. It quoted his Trig line back to him and gave him the same question, this time to ask about his own broken loops.

When the power goes out

I planned for costly internet. I didn’t plan for no electricity.

On October 19, Saikou started a farm internship in a village, which runs until late December. There’s no power on the farm. Each morning he and the other interns walk to the next village to charge their phones, and pick them up in the evening. The solar inverter that was meant to charge his laptop is broken, and the replacement doesn’t work either. His laptop can’t get through a lesson on battery.

So on October 20 the course paused. The offline design holds up fine without internet, but it still needs a charged laptop. The next lessons are written and waiting. When he can charge it, one git pull brings them in.

What I get out of it

Saikou recruited me to build a website. I’m getting at least as much out of this as he is. This course is portfolio material, and you’re reading some of it. More than that, it’s the work I want to do: teaching people to code in places where it can change what’s open to them.

Saikou read this post before it went up. The site was his idea, and so was learning to build it. I write the lessons, but he’s the one doing the work.

Sources

  1. Renkl, A., & Atkinson, R. K. (2003). Structuring the transition from example study to problem solving in cognitive skill acquisition: A cognitive load perspective. Educational Psychologist, 38(1), 15–22. ↩

Narciso Lobo designs and teaches software engineering courses. Most recently, a 14-week course for Workforce Opportunity Services. See the ASP.NET Core case study →