Being a Campus Mantri: Building a Coding Culture

For a year I served as a GeeksforGeeks Campus Mantri — the campus ambassador who's supposed to "promote a coding culture." That sentence hides a lot of unglamorous work, and it taught me more about people than about code.

The cold-start problem

The hardest part wasn't organizing workshops. It was the first ten attendees. A workshop with three people feels like a failure; a workshop with forty feels like a movement. Getting from the former to the latter is a trust problem, not a logistics problem.

What worked:

• Show up small and consistently. A weekly problem-of-the-day thread beat a one-off "big event."
• Make it specific. "DSA workshop" is vague. "Crack these 5 interview patterns in 90 minutes" gets sign-ups.
• Let attendees teach. The moment a peer presents, the room stops being a lecture and starts being a community.

What I actually did

• Organized workshops and shared resources.
• Drove participation in GeeksforGeeks events and the GfG 160 summer program.
• Spent a lot of time just answering "how do I start?" in DMs.

What it gave me

Community building is a forcing function for clarity: you can't promote what you can't explain simply. It also made me a better open-source contributor — the same skills that get ten students to a workshop get a maintainer to review your PR: show up, be specific, make it easy to say yes.

You don't need a title to do this. But the title did make me take it seriously.