Teaching
I teach in the Department of Computer Science at the University of Miami. Both courses below were written from scratch; the materials on each page are ones I authored.
Teaching philosophy
I design a course from the outcome backward. Objectives map to levels of Bloom’s taxonomy, assessments map back to objectives, and a student can always say what they are being asked to do and why. Coverage is not the goal. Working through an unfamiliar problem is.
In Python Programming for Everyone, programming is the subject, and the course is built around iteration rather than demonstration. Lectures introduce a concept far enough that students can form a model of it; labs are where they extend it, get it wrong, read the error and fix it, with in-notebook validation and an autograder, both returning feedback while the problem is still theirs. Jupyter is deliberate: it keeps the write, run, fix loop short. AI tools are prohibited for graded work, including debugging, and the exams are handwritten, so what is assessed is the student’s own grasp of the logic. Debugging is not a side activity. It is where intuition is built, and it outlasts the syntax they memorized. The applied half turns that into projects students choose, ideally inside their own discipline, ending in a capstone.
In Information Technology and Society, the hands-on work serves a different end. Most students will not become programmers; the labs are there to build confidence with unfamiliar tools, and the materials start from questions they already have a stake in. How that works in practice.
I keep the pace fast and the support high. The goal is not a floor everyone clears but removing the ceiling: an A should be achievable without becoming the place a student stops. Students use the tools they will meet in industry. The aim is not the next course. It is the next problem.
Course materials
The materials on these pages are my own work. All rights reserved; please ask before reusing them.