{"id":499,"date":"2026-06-18T14:42:44","date_gmt":"2026-06-18T21:42:44","guid":{"rendered":"https:\/\/blogs.ubc.ca\/aichallenges\/?p=499"},"modified":"2026-06-19T11:42:42","modified_gmt":"2026-06-19T18:42:42","slug":"499","status":"publish","type":"post","link":"https:\/\/blogs.ubc.ca\/aichallenges\/2026\/06\/18\/499\/","title":{"rendered":"Vibe Code Something That Makes Your Life Easier"},"content":{"rendered":"\n

<\/h1>\n\n\n\n
\n

This challenge turns vibe coding<\/em> toward the practical: building a small tool that handles a repetitive task in your teaching life. Along the way, you’ll confront one of the central tensions of AI-assisted creation the gap between it works<\/em> and I understand it<\/em>.<\/p>\n<\/blockquote>\n\n\n\n

Vibe coding shines at practical problem-solving. With a few prompts, you can build a tool that automates something tedious no setup, no syntax, no Stack Overflow. For educators drowning in small repetitive tasks, this is genuinely appealing.<\/p>\n\n\n\n

There’s a catch worth feeling firsthand. When AI writes the code, you can end up with a working tool whose inner logic you can’t fully read. This is the heart of a real debate about vibe coding: the gap between a thing that runs and a thing you actually understand. Before we ask students to navigate that gap responsibly, it’s worth experiencing it ourselves.<\/p>\n\n\n\n

Challenge<\/h3>\n\n\n\n

Build a small tool that streamlines something you do often, without writing the code yourself<\/em>. Then interrogate it: not just “does it work?” but “do I understand it well enough to trust it?”<\/p>\n\n\n\n

Pick your scenario<\/h3>\n\n\n\n

Pick a real, recurring annoyance\u2014the smaller and more specific, the better.<\/p>\n\n\n\n