Teaching Code the Way I Wish I Was Taught

I didn't become a coding instructor because I was the best student in my class. I became one because I remembered exactly what it felt like to be lost.

When I first started learning to code, I sat through lectures where the instructor would fly through concepts, assume everyone was following, and move on. I'd look around the room and see heads nodding - but I knew half of us were pretending. I was one of them.

That experience shaped everything about how I teach.

The philosophy: teach humans, not topics

At the University of Sydney bootcamp, and later at community organisations in Cape Town, I've taught hundreds of aspiring developers. Every cohort is different, but one thing stays constant: people don't learn to code from slides. They learn from someone who gives a damn.

My approach is simple. I teach the way I wish I had been taught:

Start with the "why" before the "how." Before I show a single line of JavaScript, I explain why it matters. What problem does this solve? What would you have to do without it? When students understand the motivation, the syntax sticks.

Break things down until they can't be broken further. I've watched students freeze when faced with a full CRUD application. But when I break it into steps - "first, let's just make a button that logs something to the console" - suddenly it's manageable. Confidence comes from small wins stacked on top of each other.

Normalise confusion. The most powerful thing I say in a classroom is: "This is supposed to be confusing right now." I watch shoulders drop and breathing slow down. Learning to code is hard. Pretending it's not doesn't help anyone.

Never make someone feel stupid for asking a question. I've seen instructors sigh when a student asks something "basic." That sigh costs you that student. They'll never raise their hand again. Every question is valid because it represents exactly where that person is in their learning journey.

Building real connections

One former student described me as someone who "breaks down complex topics into understandable, practical steps, making challenging subjects feel approachable." Another said my "patience and dedication to each student's success made a significant difference, especially during times when concepts felt overwhelming."

Those words mean more to me than any line of code I've ever written.

But connection isn't just about being nice. It's strategic. When a student trusts you, they'll tell you when they're stuck instead of pretending they understand. That honesty saves weeks of compound confusion. One student told me I "opened their eyes to the endless possibilities of development" and that my "presence alone has driven them to work harder." That's not about me being special - it's about creating an environment where someone feels safe enough to be ambitious.

What I've learned from my students

Teaching has made me a better developer. When you have to explain promises to someone who's never seen asynchronous code, you actually have to understand promises. Not just use them - understand them.

I've also learned that the best developers aren't always the fastest learners. Some of my strongest students were the ones who struggled the most in the first few weeks. They built resilience. They learned how to debug not just code, but their own learning process.

One colleague noted that my "approach to work shows a high level of experience in almost every facet of web development, as well as the ability to learn and apply new concepts with ease." I appreciate that, but what I'm most proud of is that I can pass that ability on.

The multiplier effect

Here's why I keep teaching even as my consulting work grows: every developer I help become competent creates a ripple effect. They build products. They teach others. They hire juniors and treat them well because they remember what it was like.

I've taught over 60 underprivileged youth at community organisations, helping them build careers in tech. Some of them are now senior developers. Some of them are teaching others. That's the real return on investment.

If you're learning to code right now

Find an instructor who makes you feel safe to fail. Find someone who answers your "stupid" questions with genuine enthusiasm. Find someone who remembers what it was like to not know.

And if you can't find that person - know that the confusion you feel right now is temporary. The fact that you're pushing through it is what separates you from everyone who thought about learning to code but never started.

You're already ahead.