Include this sentence in your initial proposal contract: 'Project includes up to 2 rounds of design revisions. Additional revision rounds or changes to approved wireframes will be billed at ₹1,500/hour.' The moment revisions have a price tag, clients suddenly become remarkably clear about what they actually want.

Change this: 'Built an API for student management system.' To this: 'Engineered 14 RESTful endpoints using Go and PostgreSQL, reducing query latency by 35% and serving 1,200 daily active campus users.' Formula: Accomplished [X] as measured by [Y], by doing [Z]. Put metrics in every single bullet point!

Classic computer architecture experiment: Iterate over 100,000 integers and conditionally sum elements > 128. If the array is unsorted, the CPU's branch predictor misses 50% of the time, stalling the instruction pipeline. If the array is sorted, branch prediction accuracy is ~99%, and execution runs 6x faster. Understanding hardware mechanics makes you a dramatically better programmer.

Question: 'Estimate the number of cups of tea consumed daily on your university campus.' 1. State clarifying assumptions (campus student population = 6,000; hosteler vs day scholar split = 80/20). 2. Segment by user personas (non-tea drinkers = 30%, light drinkers = 1 cup/day, heavy exam grinders = 3 cups/day). 3. Add faculty and canteen footfall. 4. Sanity check with canteen vendor batch sizes. Interviewers care about structured logic, not the exact number.

1. The 3-5 close friends who will pick up your call at 3 AM ten years from now. 2. The ability to learn a completely new domain from scratch in two weeks without getting overwhelmed. 3. Your health, emotional resilience, and communication skills. Keep your GPA above the eligibility cutoff (usually 7.5 or 8.0), but don't sacrifice your youth and friendships chasing a 9.8.