I learn by building projects and explaining ideas in ways that make sense to the people I am speaking with. My experience as a campus ambassador shaped how I communicate; it is also part of my background as a pinku sharma linkedin profile.
Earlier, I used to think I should finish the whole course and watch all the tutorials before starting to build.
Now I learn enough to start and let the project teach the rest.
I believe real learning happens when code breaks and I have to figure it out myself; I have described that happening at like 1 am.
For me, tutorials can create false confidence, while building and debugging make me work through what I actually need to understand.
My WhatsApp bot for farmers showed me that farmers type half the name wrong, skip fields, and send random stuff.
Building the bot taught me validation, handling garbage input, and keeping things simple in Hindi.
Classroom examples often focus on the happy path; building for real people taught me to account for incomplete, misspelled, and unrelated input. I do not have quantified outcomes or implementation details for the bot recorded here.
I saw students switch off in 10 seconds when explanations use full technical terms like a textbook.
When I explain an idea, I start with why it matters for the audience, give one real example, and keep it short.
My test of understanding is: if I cannot explain an idea to a first year in the canteen, I do not actually understand it.
Campus ambassador work made me explain ideas to ordinary students, not only CS enthusiasts. I used to rely on technical, textbook-like explanations because I thought they would make me sound smart; now I focus on relevance, a concrete example, and brevity.