I've been selected as Tech Lead of Google Developer Groups on Campus (GDGoC) at NUST SEECS for this tenure. I oversee three directorates: AI/ML, Web Development and Cybersecurity, a team of 17 people. Last year I was the Director of Cybersecurity.
I don't want this tenure to be a series of one-off events that people forget a week later. So the core of my plan is a repo.
Learn Your Own X
Learn Your Own X is a curriculum where students build small versions of real systems, one module at a time, to understand how they work underneath. It's inspired by build-your-own-x, which I've contributed to.
I was impressed by build your own x but it lacked the thing I needed when I was working on my shell. It had tutorials only I wanted something that taught me basics just enough to let me build something of my own
Each module is two things at once:
- A handout for a live workshop we run, online on Discord or in person.
- A self-paced guide for anyone else, with starter code that runs on day one and checkpoints you can verify yourself.
The first module is Git and GitHub. It ends with your first merged pull request, into this repo. I chose that deliberately: the best way to teach open source is to make the workshop itself an open-source contribution. Our first in-person workshop on it is in November.
Modules are written by members and reviewed by their domain director before I merge them. Students learn the material, and they also learn what real code review feels like.
What I'd like your help with
1. Would you join? Module 00 is the material for our first workshop. I'm also opening a Discord server where anyone, not just NUST students, can work through the modules, ask questions and get help from our team. If that's something you'd use, comment "I'd join" so I know whether to open it beyond campus. If you'd come to help others instead, say so too.
2. If you're a working engineer: what would you want to see a student in my position actually do with a role like this? What would make you take a student organizer seriously, and what's just noise?
3. If you've run a student or community tech group:
- How did you keep people coming back after the first event?
- How did you hand off work to a team without ending up doing it all yourself? This is the part I find hardest.
4. Module ideas. What's a small build that taught you how something actually works? Open a module proposal issue or comment below.
If any of this sounds useful, star the repo or drop a comment. I'll write a follow-up after the first workshop with what worked and what didn't.
PS : The event will mist likely be in late November and I am a full time student and worker so please excuse me if I am late to the chat T^T
Top comments (0)