What 100 Developer Packs Taught Us About Students

When the first hundred Developer Packs went out — free hosting, databases, and mentorship for student builders — we expected portfolio projects. Clones of well-known apps, polished for interviews. What we got instead was infrastructure for daily life: a hostel mess management system, a regional-language quiz platform, an open-source exam preparation tool.

Lesson one: students build for the ten people nearest to them. Given real infrastructure, they do not chase startup ideas — they digitize their hostel, their coaching class, their neighborhood temple's donation ledger. That software would never exist commercially, and it matters enormously locally. Supporting it is the cheapest social impact per rupee we have found.

Lesson two: office hours matter more than compute. The most-used benefit in the entire pack was not the VPS — it was thirty minutes a month with a working engineer who could say 'your schema is fine, ship it.' Students are not blocked by missing resources nearly as often as they are blocked by missing confidence.

Lesson three: documentation in plain language beats tutorials. Our builders did not want to be taught; they wanted to be unblocked. The pack's most-read page is a two-hundred-word explanation of how to point a domain at a server. We rewrote all our guides after noticing that.

Lesson four: community projects create maintainers. Three of the cohort's projects now have contributors the original builder has never met, in one case from another country. Free hosting did not just support software; it quietly created open-source maintainers who now review pull requests between lectures.

Lesson five follows from all of the above: the second cohort will be selected even more heavily for projects that serve someone. Not the flashiest demo, not the trendiest stack — a real user, however small the circle. Because that, it turns out, is where student software comes alive.