Skip to main content
Teaching Statement · TC'S HOMEPAGE

Teaching is a Design Problem.

How can I deliver courses so students learn by doing the real work of the field?

Explore the three pillar values that drive my teaching.

Infrastructure is where practice first becomes real. In large classes, it determines whether students can practice often and get feedback quickly.

450-plus student flipped classroom teams working through database exercises while staff coach.
450+ student flipped classroom. Teams work through PrairieLearn activities while course staff circulate to coach.
  • Randomized auto-grading on PrairieLearn: SQL tasks run against fresh data each submission, so students reason through errors instead of pattern-matching answers.
  • Participation visibility with Here@Illinois: co-founded and built an attendance platform now used by 7,000+ students and 100+ instructors per term.
  • Staffing for coaching: automation handles logistics so course staff can focus on guidance, not manual tracking.

Outcome: more iteration, faster correction, and more high-value instructor-student interaction in class.

Mechanisms make alignment matters enforceable. Students optimize for points, so course design must make that behavior support learning, not bypass it.

Lecture warm-up activity on linear hashing mechanics with visual scaffolding.
A warm-up lecture activity that scaffolds linear hashing mechanics before students tackle practice problems.
  • Concept-aligned milestones in CS 411: each project stage requires evidence of the current concept, from ER modeling to indexing experiments with MySQL EXPLAIN.
  • Reasoning made visible: students submit artifacts that expose design choices, making feedback concrete and discussable.
  • Rubric incentives in CS 242: clean-code credit scales with functional completeness, so maintainability and testing stay inside the main work.

Outcome: earning points becomes tightly coupled with building the target skill.

Interaction is where process over answers becomes a habit. My goal is to coach routines students can reuse, not provide one-off fixes.

Students in HCI Research Methods debating paper placement on a shared methods map wall.
Students in HCI Research Methods debate paper placements on a shared methodology map wall.
  • Debugging routine: Localize, Isolate, Test, Revise. Students use this loop across SQL, systems tasks, and programming assignments.
  • Method reasoning in HCI: paper-map walls and coding replications force students to justify research choices with evidence.
  • Transfer focus: students leave with a reusable approach for progress under uncertainty.

Outcome: students become more independent, analytical, and resilient when they get stuck.

Courses I've Taught

15 semester-long appointments across 6 courses, introductory to graduate

I can teach a wide spectrum of courses.