This site has more articles than most engineers write in a career, and students ask why I bother when the code already exists. Three reasons, in order of how much they matter to me, and one honest one about how invitations happen.
Writing is how I find out what I think
Explaining why RAG.NextUpgrad refuses to answer forced me to make the threshold logic defensible. Writing the judging rubric forced me to decide what I actually value in a student project. Half of the articles here changed the systems they describe.
Writing gives students something to point at
A mentoring conversation ends; an article stays. When a student asks how to ask for help, I send how to ask a mentor for help and the next conversation starts further along. Two hundred students mentored is possible because the answers compound.
Writing is how colleges find you
Every invitation I have received to speak, mentor or evaluate projects came from something public — a post about a session, a tutorial, a write-up of a hackathon. Coordinators search, read, and write. Nobody is invited from silence. The campus invite page exists to make that path short.
The honest reason
I want to be the person a placement officer in a tier-2 city thinks of when they need someone to talk to their students about real AI work, and the person a fest team calls when they need a judge who will give written feedback. That is a reputation, and reputations are built in public, one useful piece at a time.
For students
- Write about what you built and what broke, not about what you learned in the abstract.
- Publish where the people you want to reach already read.
- Keep a consistent name and links everywhere, so the pieces add up.
- Start before you feel qualified. Qualification arrives through the writing.
The template for a first post is in writing your first technical blog post. The rest is repetition.
— Pranjul Rathour, GenAI Engineer from Kanpur, India. Open to GenAI roles, hackathon judging, mentorship sessions and guest talks at any campus: pranjulrathour41@gmail.com.