The problem

Six courses, 20 hours a week of training and competition, and deadlines scattered across four systems that don't talk to each other: the LMS, university email, athletics compliance, and my own calendar. There was no single place to know what was due.

The constraint

The university denied my request for LMS API access. I rebuilt the ingestion path around the public calendar feed and got the same outcome inside the restriction.

What I built

A Google Apps Script pipeline that pulls from Gmail, an ICS feed and a manual entry form into one sheet, with deduplication, categorisation and notifications.

The design call I'd defend

Nothing is written without my approval. Silent automation on academic deadlines is a bad trade: a false negative costs a grade, and my eligibility depends on those grades. I optimised for control, not coverage.

Chap's OnFood

Course project · Web Programming, Lubbock Christian University

Students on campus had no way to order food ahead — ordering meant walking over and waiting in line between classes. I defined the concept, the feature set and the ordering flow, then built the site around them: menu browsing, item selection, cart and order submission.

To be clear about what it is: a working prototype, not a service the university runs. No real orders go anywhere. What it shows is that I take a vague problem, decide what the thing should actually do, and ship something that runs.