The advice "write about your projects" is easy to give and hard to act on the first time, because most students don't know what makes a build log different from a README.
The template I use
- Open on a specific moment — a bug, a constraint, a decision — not a general introduction to the topic.
- State the real constraint you were working under: hardware, time, team size, budget.
- Walk through 2-3 decisions and the alternative you didn't pick, and why.
- Admit what you'd do differently. This is the paragraph most people skip, and it's the one that makes a post feel honest instead of promotional.
- End with one specific takeaway a reader could apply to their own project this week.
Why numbers beat adjectives
"Runs efficiently" tells a reader nothing. "Runs in 220 MB on a free tier" tells them something they can act on or compare against their own project.
Post it before it feels ready
The version you're slightly embarrassed to publish is usually the one worth publishing. Waiting for a post to feel complete is how most people never publish one at all.
GenAI engineer and AI product builder with 2+ years shipping production-grade AI systems: RAG pipelines, fine-tuned LLMs, hybrid retrieval and multi-modal apps across vision, speech and OCR, architected end to end from ingestion to deployment. Leads engineering for SCULT INDIA's 14-member team, founded the 500+ member TechVerse Enclave community and has mentored 200+ students. Three hackathon first prizes: Changethon 2025 (IIT Roorkee), Product Genesis at Vividhotsava 2025 (CSJMU Kanpur) and BYTEBATTLE (MeetKats).
Open to GenAI roles, hackathon judging, mentorship sessions and guest talks at colleges. Email pranjulrathour41@gmail.com.
