Dev Weekends

When I joined university, I got lucky. I found mentors early who helped me get on track. That alone made a difference.

Then I joined the Microsoft Student Partner program. Back then, Microsoft had a local evangelism team in Pakistan. I learned from them. How to teach. How to run events. How to get people excited about technology and actually help them move forward.

I took that and ran with it. Built the IT Society at university. Delivered 200+ sessions over four years. Learned what actually works when you're trying to help someone level up, and what doesn't.

By the time I graduated, I had a question: what happens to the people who didn't get lucky? The early career engineers who are already working but don't have time to figure everything out on their own? The self-taught developers who don't know what to learn next?

That's where Dev Weekends started.

The idea was simple. Take everything I learned in four years of evangelism and mentorship and apply it to a new format. We started on weekends because that's when working professionals could actually show up. The name stuck long after the schedule stopped being only weekends.

The gap we saw

Universities in Pakistan, and honestly most places, teach syntax. They don't teach systems thinking. They don't teach you how to debug a production issue at 2 AM or how to read a codebase written by someone who left the company three years ago.

Three problems kept showing up.

The education gap. Universities teach you to pass exams. Industry needs you to ship products. The distance between "I can write a for-loop" and "I can architect a system that handles 10,000 concurrent users" is vast. Nothing in the curriculum bridges it.

No roadmap. Brilliant minds stuck without direction. A kid in Lahore with genuine talent doesn't know whether to learn React or Angular, whether to focus on DSA or system design, whether open source matters or is a waste of time. There's no mentor to say "here's what actually matters."

Learning alone. Self-teaching is romanticized but brutal. Without community, without accountability, without someone to tell you "you're on the right track," most people burn out or drift.

What eight years built

This thing grew into something I didn't expect.

30,000+ community members across 7 countries. Not just passive followers. People actually engaging. The Discord is active almost every day. Conversations happening, people helping each other debug code at midnight, celebrating wins, sharing rejections and figuring out what to do next.

1000+ freelancers in the community sharing work, helping each other find gigs, learning from sessions on freelance engineering. Recruiters actively rely on our community for hiring. When companies need talent, they come to us.

Five different reading sessions where we meet once a week to go through books or series of engineering topics together over Discord. System design, clean architecture, whatever the group wants to dig into. One thing I learned: people don't just need information, they need a group to process it with.

We've run ongoing series on automation testing, deep engineering topics, cloud and DevOps, AI and ML, and freelance engineering. Not one-off sessions but sustained series where people build real understanding over time.

Mind Masters

This one is different from the technical stuff.

We started Mind Masters because we noticed something: you can't build a career if you're burning out. A lot of our members were technically capable but stuck. Procrastinating. Overwhelmed. Lacking direction.

Mind Masters is about understanding your brain. Building discipline. Being more productive. Finding a true purpose in life.

It's an invite-only community for engineers who understand that growth happens beyond the keyboard. We've had sessions on the psychology of excellence, time and energy mastery, brain and mental health, how to let go, and the spiritual dimension of work and life. We do Talk of the Week, Talk of the Month, Book of the Week, Book of the Month. Curated content from the world's best thinkers on performance and meaning.

The outcomes

Numbers matter because they represent real people whose lives changed:

• 200+ placements per year through our network
• 500+ LeetCode Centurions, probably closer to 700+, but we don't always count
• 2 GSoC acceptances
• 30+ actively contributing to open source
• 20+ engineers placed at Turing alone
• 71% career placement rate
• 18% completion rate, which we're still working to improve

People landing jobs at startups in Europe, at companies they'd only seen in tech news. In Pakistan's ecosystem, open source contributions, GSoC acceptances, competitive programming culture, this stuff doesn't happen. It's not the norm. We're building something that didn't exist before.

Why it's free

We had serious conversations about charging. Other bootcamps charge thousands. They have marketing. They promise outcomes.

But the people who need this most can't afford it. The kid in Lahore whose family makes $400 a month. The self-taught developer in a small town who keeps getting rejected because they don't have the "right" background.

That's who we built this for.

The chain continues. Equipment sponsors help us provide laptops and registration fees for students who can't afford them. 100% of donations go directly to student support.

Where the weekends led

Everything we did in those first years worked. I want to be clear about that. The community model, the sessions, the reading groups, the freelancer network, Mind Masters. It helped a lot of people.

But the casual drop-in culture meant some people drifted. They'd attend for a few months, learn some things, then disappear. Not because they weren't talented. Because there was no structure pushing them through the hard parts.

So in early 2025 we built something on top of it, with tracks, milestones and accountability. Same spirit, more structure.

That's the Fellowship, and it's the part people ask about most.

Read how the Fellowship works