Georgia Tech Curriculum

The brief

For six years I was the lead instructor for a full-stack program, running cohorts of fifteen-plus students at a time. The harder, more interesting job came later: a full overhaul of the curriculum itself, treating it as a system with inputs, feedback, and outcomes rather than a static syllabus.

What I built

The overhaul modernized the whole stack a student moves through. It added AI and LangChain, moved core material onto TypeScript, introduced CI/CD and test-driven development as habits rather than topics, and added a Python module. The goal was a curriculum that compiles, in the sense that the path from day one to a shippable project is tested, current, and repeatable across instructors and cohorts.

Why it belongs here

Directing a program and re-architecting its curriculum is systems work and team direction, not a detour from engineering. It is where I learned to design something that has to keep working when many different people run it.