Ban 'it's easy' from your classroom
The two words that quietly filter out half your future engineers — and what to say instead when a student is stuck.
cat post.md →12 years teaching Computer Science to Grades 6–12, after four as a software engineer. My students ship real projects — a canteen queue app, the school's event portal — because programming is a thing you do, not a chapter you memorise. Girls make up half my senior CS batch, and I intend to keep it that way.
I spent four years as a software engineer and kept noticing the same thing: the best engineers weren't the ones who'd memorised syntax at seventeen — they were the ones nobody had ever told coding wasn't for them. Meanwhile school CS was busy telling exactly that to girls, arts students, and anyone who blinked at semicolons. I switched to teaching to fix the pipeline at the source.
Twelve years in: my students have shipped 46 real applications, including the canteen queue app the school actually uses (peak load: Friday samosa day) and the event portal that survived 3,000 concurrent parents. My senior CS batch is 50% girls — up from 12% when I arrived — because week one is designed so nobody gets to feel behind. Board average: 97%.
If your school wants computer science taught by someone who has shipped production code and can explain a for-loop to a poet — merge me in. I review my own work harshly.
Twelve years from block coding to compilers — no deprecated methods.
Most school CS is history of computers plus syntax dictation — a programming course with no programs. Mine inverts it. Week one, everyone ships something tiny and real. Then every concept — loops, functions, complexity — arrives as the fix for a problem their own code just hit. while(confused) we explain differently; we never say "it's easy".
Lead a four-teacher department. Built the ship-real-projects curriculum (46 apps live), the girls-in-CS pipeline (12% → 50% of Grade 12), and the school's student-run tech team that maintains the event portal. 97% board average.
Grades 6–12; replaced 'history of computers' term with week-one shipping, and watched enrolment in senior CS double in two years.
Backend services; learned production discipline, code review culture, and that the error message is always trying to help. Left to fix the pipeline at the source.
The two words that quietly filter out half your future engineers — and what to say instead when a student is stuck.
cat post.md →Why my course starts with running code in every hand before a single definition — and how it rewired who signs up for CS.
cat post.md →A classroom protocol for reading stack traces like friendly letters. Debugging is the literacy; syntax is just spelling.
cat post.md →My daughter said CS wasn't for people like her. One term with Ms. Rao and she's built a period-tracker app her friends actually use. She's doing B.Tech now.
Kavya's motherPARENT · GR 12The canteen app her students built has genuinely reduced Friday chaos. When it went down once, the whole school noticed. That's real software.
PrincipalNPS BENGALURUI'm an SDE now and I still hear her voice when I read a stack trace: 'it's a letter, not an accusation'. Best debugging habit I own.
ArjunALUMNUS · SDE, FLIPKART