Teaching Python before explaining technical things became part of the job.
Six months teaching programming to students from early teens to 18, and an early lesson in how much technical communication matters.
Why I did it
I’ve always enjoyed explaining things, not just knowing the answer but finding the version of the explanation that makes sense to the person in front of me.
In 2021, I got the opportunity to teach Python at Sharkcoders, a technology school for young students. I ended up teaching three groups for around six months, with students ranging from roughly 11 or 12 years old to 18 and with very different levels of experience.
The same idea needs different language
The Python was only part of the challenge. Different ages and different levels meant constantly changing the way I explained the same idea.
Some students needed analogies, drawings and very concrete examples, while others were already ready to experiment, break things and build more independently. Over those months I watched students go from basic programming concepts to projects that were genuinely impressive for their age.
How it ended
I eventually stopped teaching because fitting the schedule around my main job became difficult. Before leaving, I also got involved in early conversations around a new AI / Data Science course the school was exploring, giving feedback and technical input to the pedagogical director.
Six months was not very long, but the experience stuck with me. It made me realise that I genuinely enjoy taking something technical and finding the version that clicks for whoever is listening.
Turns out that became useful much more often than I expected!
What I took from it
Teaching forces clarity
If I cannot explain something simply, there is a good chance I do not understand it as well as I think I do.
Communication depends on the audience
The same technical idea can need completely different language depending on who is listening.