AI Slop, with No Warranty: A Year of Vibe Coding in Higher EdOctober 5, 12026
Facilitators:D'Arcy Norman (Taylor Institute for Teaching and Learning at the University of Calgary)
Brian Lamb (Centre for Open and Engaged Learning at Thompson Rivers University)
Host: Harper Friedman
Online learning platforms in higher ed are now mostly enterprise applications on campus-scale licenses, leaving little room for small-scale experimentation. Prototyping matters for developing and evaluating educational technology, but it has traditionally needed teams of developers working over weeks or months, often across institutions. Frontier models with integrated coding harnesses (Claude Code, Google Antigravity, OpenAI Codex) have changed that. One person can take an idea to a usable prototype in hours, then deploy it and even integrate it with the LMS.
D'Arcy and Brian share their approaches to "vibe coding" as a way to explore and test ideas with functional prototypes, not to replace conventional software development.
When Google retired Jamboard, D'Arcy Norman built a replacement, Jellyboard, with Claude Code and put it at jellyboard.ca. He labels the source "AI Slop, with no warranty," and uses it in retreats at the University of Calgary. His vibecoding tag at darcynorman.net also shares a Brightspace "Socratic coach," a self-hosted bookmarks app built over 46 sessions, and an Obsidian plugin powered by vector embeddings.
Brian Lamb's posts on abject.ca describe a resource activity builder for TRU's Open Press materials, a team diagnostic, and an anatomy study companion built into Moodle. This is already happening inside our institutions, whether procurement has heard about it or not. The best and worst things about vibe coding are both that anyone can build, and nothing holds them back or keeps things safe. The risks are real: pollution of shared infrastructure, security and privacy harms outrunning policy, quiet deskilling of practice. We want to tour the artefacts, learn what broke and what worked, and find out what it means for infrastructure, privacy, accessibility, budgeting, maintenance, and academic integrity once a vibe-coded tool crosses from "scratched my own itch" into the university.
Attachments: Transcript (PDF, Word, Text)
Note: If you notice an error in the closed-captions (or transcript file), please email support@bccampus.ca with details of the error, the time stamp, and your suggested correction, if any.