We met through robotics, we stayed friends through robotics, and now we teach robotics. Funny how that works.
Arham is the reason every session had exactly enough components, working laptops, and not a single missing wire. Led the hardware side, kept the project ops running, and basically built the on-the-ground machinery that made the whole thing possible. Also gives the best 'okay try it now' face in the business.
The one who sketches every circuit out by hand before we touch a breadboard. Zeus led the electricity-and-circuits arc of the curriculum, and is the reason every session had at least one demo that actually worked the first time. Long-time tinkerer, professional finder-of-shorted-wires, and an extremely patient explainer.
Rehaan ran the coding side of things — pseudocode workshops, microcontroller intros, the whole 'turning student ideas into real syntax' workflow. Has the rare ability to explain a for-loop to a Grade 6 student without anyone glazing over. Believes pseudocode is underrated and will defend that opinion at length.
Sessions are planned the weekend before. Materials are checked twice — once by whoever's leading the session, once by whoever isn't. We use Notion for schedules, timelines and progress trackers, and Google Drive for the chaos of receipts, photos, scanned student worksheets and the occasional "wait, where did the lesson plan go?" moments. We debrief after every session, no exceptions. The retro is short but honest. That's the whole secret.