3 posts tagged with "Reflections"

Fall 2016​

A Community Born from Necessity

I was three weeks into university when I realized something was missing. The campus buzzed with tech clubs, sponsored by names everyone recognized (Mozilla, Microsoft, etc), but their calendars were filled with formals, branding events, and administrative formalities. Actual conversations about code, systems, and the open‑source philosophy were rare.

I wanted a space where computer scientists could simply build, share, and learn without hierarchy. A place where a first‑year student could sit beside someone who’d been contributing in tech for years, and both would walk away having taught each other something.

Inception​

In ALiAS, what mattered first was the gathering. A few of us began meeting in empty classrooms, running installation fests, and talking late into the evening about kernels, pull requests, and why open source mattered. Shyam Saini and Shivam Rajput were there from the earliest conversations, confirming I wasn’t alone. Over the next few months, others joined, each drawn by the same hunger for genuine technical community.

This is how ALiAS, Amity Linux Assistance Sapience, was born. A name that captured the identity we were creating for tech enthusiasts who believed in open source, accessibility and exploration.

From those small beginnings, ALiAS grew into something larger than any of us expected. But the foundation was always the same: a flat, inclusive space where curiosity mattered more than credentials. Our vision was simple, to create an accessible environment where collaboration, knowledge sharing, and personal growth could happen naturally, without the barriers that often fragment student communities.

Roles and Responsibilities​

A strong community needs structure to direct the immense energy sparked from enthusiasm. For this, ALiAS was designed around a flat hierarchy, deliberately avoiding rigid titles so that members could take ownership of areas aligned with their strengths. This approach allowed me to delegate strategically while ensuring that every aspect of the community received focused attention.

• Community ethos and leadership – I entrusted key members to uphold the vision in day‑to‑day decisions, providing guidance while allowing them to lead in their own style.
• Inclusivity and communication – I personally shaped the communication framework and inclusivity practices, setting the tone for how we onboarded members, handled conflict, and made sure every voice was heard.
• Technical development – I established a technical mentorship structure, pairing experienced contributors with newcomers to maintain high code quality and encourage knowledge transfer.
• Event logistics – I designed a workflow for planning and executing events, empowering members to run operations while I oversaw alignment with our long‑term goals.
• Content and documentation – I created systems for documenting our work and creating accessible learning materials, ensuring that knowledge outlived any single event.
• Outreach and partnerships – I led external engagement, connecting with industry mentors, faculty, and organizations to expand our network and bring new opportunities to the community.

⠀This structure gave each area the focused attention it needed while keeping the organization agile—and it allowed me to scale my impact by enabling others to lead within clear guardrails.

Growth and Milestones​

From small workshops to large‑scale annual events like Hacktoberfest, I deliberately chose activities that would build both technical skills and a sense of shared purpose. Some of the initiatives I launched or led include:

• Monthly Linux Installation Fests – Introducing students to Linux and helping them get started with a powerful open‑source environment.
• Daily Tech Meetups – Creating a regular forum for discussing the latest technological advancements and sharing insights across the community.
• Community Calls – Establishing a rhythm of planning meetings to continually refine ALiAS’s direction and expand its reach.
• Specialized Study Groups – Organizing peer‑led groups in areas like frontend development and machine learning, with support from faculty collaborators.
• Annual Hacktoberfest events – Introducing students to open‑source contribution and helping them make their first pull requests in a supportive environment.

⠀Beyond events, I also drove the creation of a community blog—a platform for members to share technical insights and experiences, which became a key tool for building our reputation beyond campus.

These efforts did more than grow numbers; they created a culture where students felt empowered to lead their own initiatives. I made it a priority to identify emerging leaders and give them the space to run workshops, mentor peers, and eventually start their own chapters elsewhere.

Linux Study Group with Prof. Priya Ranjan​

One of the most rewarding collaborations came through Prof. Priya Ranjan, a Linux enthusiast in the Electrical and Electronics department who had been running weekend study groups for years. We began co‑organizing sessions that combined his deep technical expertise with ALiAS’s growing community of learners. His ability to explain complex systems in simple terms left a lasting mark on how I thought about teaching and mentorship.

Overcoming Challenges​

No community‑building journey is without obstacles. Navigating university bureaucracy, engaging a broader student base in open‑source contributions, and addressing gaps in participation all required persistence and adaptability. Each challenge became an opportunity to refine my approach—whether it was learning how to negotiate with administrators or redesigning outreach strategies to reach students who hadn’t yet found a technical home.

Bridging Gaps​

Enhancing Women’s Participation in Tech Despite our growth, the gender ratio in tech remained skewed. Of the founding members, only two of us were women, and participation reflected that imbalance. I knew that passive inclusion wasn’t enough—so I initiated targeted efforts to change the dynamic.

I organized workshops and events specifically designed to welcome women into tech spaces, including Women’s Day tech talks featuring prominent contributors like Shivani Bhardawaj of LinuxChix India.

Beyond events, I started a personal mentorship program where I guided women students through career choices, skill development, and navigating the tech landscape. These efforts significantly boosted female participation and, more importantly, brought diverse perspectives into the heart of the community.

Impact​

The impact of these efforts became visible in tangible ways. ALiAS was recognized as the most active tech club on campus—a distinction that carried weight when I later advocated for curriculum changes. Working with faculty and administration, I helped make the case for introducing Python into formal coursework, a change that benefited students across departments.

Expansion​

The Rise of ALiAS Chapters The model we built—a flat, inclusive, student‑led community—proved replicable. When students from Amity University, Lucknow, expressed interest in starting their own chapter, I provided guidance, shared our resources, and helped them adapt the framework to their context. That first chapter became a blueprint, and soon ALiAS chapters began emerging across India, each carrying forward the same ethos of open‑source advocacy and community‑driven learning.

Looking Ahead​

Today, ALiAS has grown to over 4,000 members across multiple chapters. Students who once attended their first installation fest now contribute to major open‑source projects, speak at conferences, and mentor the next generation. The mentorship programs I helped establish, along with initiatives like GSoC sessions, continue to guide new waves of technologists.

Reflection​

Looking back, building ALiAS taught me that sustainable communities are built on clear systems, not just enthusiasm. I learned how to design structures that empower others while maintaining strategic direction—a skill I now rely on in everything I do. More than anything, I saw that when you give people ownership and hold a clear vision, they will surprise you with what they can achieve.

This journey also deepened my conviction that technology is at its best when it is collaborative, inclusive, and rooted in genuine curiosity. Those principles continue to shape how I approach problems, lead teams, and contribute to the open‑source ecosystem. ALiAS was never just a club—it was a proving ground for the kind of technologist and leader I wanted to become.

The Start of It All

Embracing the Unexpected​

When high school ended, like countless others, I harbored certain dreams I believed that only through such accomplishments could I truly excel and achieve my aspirations. However, life had other plans, and my journey veered onto an unexpectedly rewarding path.

Discovering My Passion Locally​

The aforementioned setback steered me towards an equally fulfilling educational experience. It was here, amidst modest beginnings, that I found my true calling.

In September 2016, two months into my freshman year, our alumni organized a workshop that introduced us to Python, Linux, and the Kivy framework for developing Natural User Interfaces. This event wasn't just about coding; it was a gateway to the broader open-source community and a dormant tech club at our university, known as ALiAS. This club, they shared, was pivotal in their professional success and eventually was mine as well after I set on a journey to revive it which I have written about in the ALiAS section.

A Lesson in Community and Open Source​

The hands-on session in Linux and Python wasn't just about learning new tools—it was about understanding the ethos of giving back and collaborating.

I realized that Computer Science was more than day-to-day coding; it was about exploration, innovation, and community.

The stories from our alumni during the workshop weren't just inspiring; they answered a deep-seated question I'd often pondered during uninspiring high school computer classes: "Is this all there is to Computer Science?" The answer, resoundingly, was no.

Expanding My Horizons​

Inspired, I sought out more experiences. I attended the first meetup of ILUG-Delhi and soon after, joined sessions with PyDelhi and LinuxChix India. These groups introduced me to a network of experienced tech enthusiasts who were always ready to lend a hand or share knowledge. The core of these meetups—diverse tech talks—opened my eyes to the vast possibilities within the tech industry.

My Journey in Open Source​

I was particularly drawn to the open-source community, where I could contribute to projects that aligned with my interests and values. My contributions to Pandas and LinuxChix India are a testament to my commitment to the open-source ethos.

I have also volunteered to organise and speak at various tech meetups and conferences, including PyCon India, PyDelhi, and ILUG-Delhi. These experiences have not only honed my technical skills but also helped me build a strong network of like-minded individuals.

Recognizing My 'Luck'​

At each event, people would often remark, "Oh, how lucky you are!" to have discovered these groups so early in my career. While I appreciate their sentiment, I believe my 'luck' isn't merely coincidental. It's the result of my efforts to seize every learning opportunity, driven by a genuine passion for technology.

The True Meaning of Luck​

This journey has taught me that luck in tech, or in any field, isn't about serendipity. It's about hard work, community engagement, and the continuous pursuit of knowledge. Each step in this journey, from attending workshops to contributing to tech meetups, has reinforced my belief that when you love what you do, the right opportunities will follow.

Looking Ahead​

I am now looking forward to connect with like-minded individuals who share my enthusiasm for technology and community, and with whom I can explore new technologies, tackle projects, and enjoy the profound satisfaction of giving back.

Final Thoughts​

To anyone embarking on their tech journey, remember that your path might not always align with your initial plans. Embrace it. Sometimes, the unexpected routes are the most enriching ones. Indeed, I am lucky, not just in being in the right place at the right time, but in choosing to dive deeply into the opportunities presented to me.

A story about a Prime Minister’s felicitation, family doubt, and learning to trust my own compass

When I was starting high school, I was at crossroads of chosing a stream of courses, as goes in the Indian education system. I had to decide between studying either economics or computer science. AI hadn’t yet become a household buzzword. My family, with roots in multi-industry business, saw computer science as a narrow, uncertain path, especially when not having enough examples in their experiences to validate the path. Economics, on the other hand, was respectable, versatile, safe and would most importantly keep the doors wide open, in a traditional sense, for all of business, academia and government services.

I chose computer science.

My reasoning was mainly a hidden passion with a flavor of practicality that computer science is a skill‑based knowledge. While I spent my afternoons and nights tinkering with my personal computer, I could see myself wanting to learn it deeply under structured guidance and practice. Economics, I believed, was something I could pick up later if I chose to run a business, through life. ^[1] I couldn’t explain this well at sixteen. I only knew I had to try.

The skepticism was polite at first, then persistent. “Are you sure? You might regret this.” I wasn’t sure, how well my statements made sense. I just knew I have always had a lovely relationship with computers and I would like to maintain it.

Years later, when high school was done where I had performed the highest in the computer science subject than any other, and now I was in uni pursuing my Bachelors in the subject, I came across an email that I would brush off in a first glance as spam.

I had been selected for felicitation by Narendra Modi, the Prime Minister of India at the time, for one of the early active participation in digital governance. The invitation felt surreal. I told my parents as they lived through their usual, rushed daily life, brushing it off as spam without even looking at the screen. Digital scams were really too active then and it was an extraordinary claim to accept when not having seen a physical evidence. So I didn’t go.

Weeks later, the ceremony aired on national television. My family was gathered in the living room when the segment began. There, on screen, were the dignitaries, the venue, the very event I had described. Looking at fellows get felicitated by the Prime Minister, my dad turned to me. “Why aren’t you doing such rewarding deeds?”

I exclaimed, “You called it a scam when I told you!”. A little sheepishly with a hint of pride they looked at the email that I hadn’t yet deleted.

Did my family stop questioning my plans after that? Not entirely. The pattern had started earlier, and it would continue.

In college, I threw myself into building ALiAS, a community for Linux and open‑source enthusiasts. I organized events, attended meetups, spent evenings in empty classrooms talking about kernels and pull requests. To my family, it looked like I was spending time and money on something with no clear return.

“Shouldn’t you focus on your studies?” they’d ask. “Is this really worth it?”

I didn’t have an answer that would satisfy them. I only knew that building something alongside passionate people felt more valuable than any grade. So I kept going.

Over time, the community grew. ALiAS became the most active tech club on campus. We introduced Python into the university curriculum. Students made their first open‑source contributions. Chapters began appearing in other cities. The recognition came, not just in awards like the Shri Baljit Shastri Award for being the Best in Human Values in my entire university, but in the quiet satisfaction of seeing me mentor others and help them come out of problems I was once drowned in.

My family saw it, too. The same relatives who had questioned my choice of computer science began pursuing master’s degrees in the field. The same parents who doubted the value of my “meetings” started asking about the next event. They didn’t apologize. That’s not how it works in an Asian household. But they no longer doubted.

My family, like any higher genration, wanted me to be safe externally while I was chosing it in trusting my own compass even when the map was unclear.

Now, when I make a decision that looks uncertain from the outside, I welcome the questions. They help me see perspectives I might have missed. The final direction comes from within.

Reflecting, when I see someone navigate a similarly uncertain path, I aim to offer what I would need, that is, trust without the wight of conditions.

Patience, though not easy, is well worth it when doing the slow, steady work of building something worth believing in.

Eventually, the evidence arrives on its own. You just need to show up.

---

[1]: Here, the value of economics in my life was put up for more on-ground applicability like running a business, rather than an in-depth understanding of the subject.