Predict before you run
The single highest-leverage habit in CS education costs one minute of ink per program. Here's five years of before/after marks to prove it…
read() →My first program was ten lines of BASIC that drew a spiral, written on a 386 my father brought home in a monsoon. It ran on the fourth try. I have been chasing that fourth-try feeling ever since — and building classrooms where students get to chase it too.
Twelve years in, my lab runs on three rules: predict before you run, break what you build, and explain it to someone else. Marks follow understanding the way output follows code — reliably, and in order.
I coach the Informatics Olympiad squad, run a girls-who-code club that outgrew its room twice, and maintain the school's attendance system myself (uptime: better than the electricity).
If your school wants CS taught as a way of thinking rather than a list of definitions, my terminal is open.
rohit --verboseAnyone can fix a semicolon. I teach students to fix the idea that put it there.
Rohit Verma's view: Programming is the closest school gets to teaching honesty: the computer does exactly what you said, never what you meant. Students who learn to close that gap — between intention and instruction — carry it into every subject and, eventually, every job.
Rebuilt the curriculum Python-first across Gr 6–12. Board results at 97%; lab uptime better. Started the girls-who-code club — 8 members then, 94 now, two national hackathon wins.
+2,400 students-1 dead language (yes, that one)Took the Olympiad programme from zero to 14 medals. Wrote the school's first CS lab manual that students actually read — because it was full of bugs to find, on purpose.
+2,400 students-1 dead language (yes, that one)First posting. Twenty machines, one projector, infinite chalk. Learned that a class that laughs at segfaults together, debugs together.
+2,400 students-1 dead language (yes, that one)Replace these placeholders with real photos in the admin panel.
The single highest-leverage habit in CS education costs one minute of ink per program. Here's five years of before/after marks to prove it…
read() →Rubrics that reward working ugly code over broken beautiful code — and why style marks come last, like dessert…
read() →I keep one deliberately slow PC in the lab. Students who write O(n²) meet it eventually. It has taught complexity better than I ever did…
read() →“Sir made us predict output on paper for a month before touching the keyboard. I hated it. Then I topped districts. I get it now.”
Advait K.Batch of 2024, IOI camp selectee“Our CS enrolment doubled and the girls-who-code club has a waitlist. Rohit built a culture, not just a department.”
PrincipalBatch of 2024, IOI camp selectee“He debugged my daughter's confidence, not just her code. She's at IIIT now.”
ParentBatch of 2024, IOI camp selectee