A lot of "build in public" advice assumes you already have an audience and plenty of time. If you're a student in India with 40 followers and exams in three weeks, a lot of it doesn't fit.
I'm Vishal, and I build Vigilante and the other OCIX products from India. This is a practical guide for student developers building and sharing their work from here.
Why bother
Building in public does three things for a student developer, roughly in this order:
- It keeps you going. Posting regularly about a project means you have to keep working on it to have something to post.
- It makes your work findable. A profile with real projects and a visible history says more than a CV line.
- It connects you. The people who reply to a daily build log are usually building something too. Some become friends, collaborators or users.
Notice what's not on the list: going viral. Most build-in-public posts get a handful of likes. That's normal, and the value is still there.
Post the work, not the vibe
The most common mistake is posting about effort instead of output.
- ❌ "Day 23: grinding hard today, no days off 💪"
- ✅ "Day 23: login now survives a page refresh. Was storing the token in memory only. Moved it to an httpOnly cookie."
The second post is useful to someone else, shows you can think, and is something you'll be glad to read back in a year. A good daily post has:
- the day number;
- what changed (one sentence);
- one thing you learned or got stuck on;
- one picture: a screenshot, a diagram or a short clip.
That's why we made Vigilante's daily share card the way it is: a picture of your town, the day number and that day's verified commits. It records that day's verified work and gives you a concrete update to share.
Timing for a global audience
Indian evenings line up nicely with the American morning:
- 7:00 pm IST: 9:30 am US Eastern and 2:30 pm UK time in summer.
- 9:00 pm IST: 11:30 am US Eastern and 4:30 pm UK time in summer.
- 11:00 pm IST: 1:30 pm US Eastern and 6:30 pm UK time in summer.
(US Eastern is 9½ hours behind IST in summer and 10½ in winter.)
If you post at 1 pm IST, most of the US is asleep. If you post at 9 pm IST, the US is at work and Europe is finishing for the day. For an Indian audience, early evening is a sensible starting point. Test it against your own replies rather than trusting any rule, including this one.
Talking about small numbers
At some point you'll want to share numbers: users, signups, revenue. When they're small, it's tempting either to hide them or to inflate them ("hundreds of developers love it!").
Don't inflate. Ever. Small numbers posted honestly are interesting: "first paying user" is a great post. Inflated numbers get found out, and people remember.
You also don't have to share everything. A reasonable rule: share numbers you'd be comfortable with a future employer, investor or customer reading, and leave out the rest.
Exams, family and real life
Student life has hard edges that "post every day" advice ignores: exams, placements, festivals, family travel.
Plan for them:
- Lower the floor, don't stop. In exam weeks, a tiny daily commit and a one-line post keeps the habit and the audience. "Day 41: exam week, fixed one bug" is a perfectly good post.
- Announce breaks. "Back after exams on the 20th" is better than silence. People respect a planned break.
- Don't let the challenge become the stress. If a public streak is making a hard month harder, pause it. Your project and your health matter more than a number.
I finished my own #100DaysOfCode with every day verified on GitHub.
Selling from India
If your project ever charges money, India has its own practicalities:
- Price in rupees. Indian users expect ₹ and UPI. A dollar price signals "not for you". We show ₹ to visitors from India and $ to everyone else, with a switch to change it. (I wrote up how we pick the currency.)
- Use a provider that handles UPI and cards. We use Razorpay.
- Keep it honest. Prepaid plans with no surprise renewals and a clear refund policy build trust faster than any discount.
- Know when you need a registered business. OCIX currently operates under Vishal Pandey as an individual. Our plan is to register the business before paid institutional deals; that is our operating decision, not a rule to copy without checking your own requirements.
Handling the internet
Building in public means some strangers will be unkind. A few rules that help:
- Reply to questions, not to insults. Most negative comments don't need a reply.
- Take real criticism seriously. "Your landing page doesn't say what this does" is a gift, even if it stings.
- Don't argue about your nationality, college or English. Let the work answer.
A starting plan
- Pick one project.
- Set a small daily floor: one real commit.
- Post one factual line a day for 30 days, with a picture.
- Reply to everyone who replies to you.
- On day 30, read your posts back. That's your portfolio.
If you want the daily tracking and the share card handled for you, Vigilante is free: connect GitHub, pick your repo, and every verified day gives you something real to post.