OIM3690 - AI-Powered Web Development

2026 Spring

Session 26 - Demo Day (4/28)

contain

Today's Agenda

  • Demo Day
    • Gallery Walk (three rounds)
    • Peer Voting
  • Course Wrap-Up
    • What We've Built This Semester
    • Where to Go from Here
    • Final Thoughts

Announcements/Updates

  • Final Project - Final submission (code + README) due 5/1 (Thu)
  • Weekly Learning Logs - Last one: wk14.md
    • Reflect on Demo Day and the semester overall
  • Communication
    • Office Hours: Walk-in or by appointment
    • Email: Specify course # in subject, e.g., "OIM3690: GitHub settings"
    • You are required to meet with me at least once this semester
  • Questions?

Student Experience Questionnaire (10 mins)

  • Canvas - Left Panel - Student Evaluation Questionnaire (SEQ)

Demo Day: Gallery Walk

Before We Start

Go to oim3690.github.io/demo-day-vote

  1. Log in:
    • Username: Your Babson username
    • Password: Your first name typed twice, all lowercase
  2. Check that your project shows up correctly
  3. If your site isn't deployed yet: upload a screenshot and add your project name
  4. Make sure your project link works

We'll start the gallery walk once everyone is set.

How It Works

Three rounds, ~10 minutes each.

  • Round 1: Group A presents, Groups B + C observe
  • Round 2: Group B presents, Groups A + C observe
  • Round 3: Group C presents, Groups A + B observe
  • Free Round (~5 min): Visit anyone you missed, including your own group

As a presenter: Have your project open. ~2 min walkthrough: what it does, how you built it, what was hardest.

As an observer: Visit as many projects as you can. Ask questions, take notes for voting.

Group A (Round 1) Group B (Round 2) Group C (Round 3)
Lucian Gabriella Lexie
Zander Aaryan Tamanna
Julissa Johannes Gavin
Hazuri Jacob Charles
Joana Simon Ariana
Sophia Miranda Sofia
Pablo Sumair Kabir
Seyvik Lan Viraj
Kelly Davina Isabel
Caroline Santiago

What to Ask as an Observer

  • What problem does your project solve?
  • What was the hardest part?
  • Which AI tools did you use? How did they help?
  • What would you add with more time?
  • What's one thing you learned that surprised you?

Take mental notes. You'll vote after all three rounds.

Voting

Peer Voting

After all three gallery walk rounds:

Best Project (MVP vote): Pick your Top 3 (#1 = 3pts, #2 = 2pts, #3 = 1pt)

  • Top 3 overall earn extra credit: +3 / +2 / +1

Special Awards (1 vote each, winner gets +1):

  • Most Fun - Most entertaining or enjoyable to use
  • Most Useful - Solves a real problem

Voting link will be shared after the gallery walk.

Course Wrap-Up

13 Weeks Ago...

  • You had little or no knowledge about programming
  • You stared at HTML, CSS, or JavaScript and saw gibberish
  • You had not used VS Code or GitHub
  • You had never created or managed a website
  • You had never deployed something to a public URL anyone could visit
  • You had never processed data from an API
  • You had never used AI tools as a coding partner, not just a homework helper
  • You had never experienced the joy and challenges of creative problem-solving
  • You probably didn't think of yourself as a builder.

Today? Look at what you just demoed.

What We've Built This Semester

  • How the Web Works - DNS, HTTP, client-server model
  • Tools - Git, GitHub, GitHub Pages, Copilot, DevTools
  • HTML - Document structure, semantic tags, accessibility, forms
  • CSS - Selectors, box model, Flexbox/Grid, responsive design, frameworks
  • JavaScript - DOM, events, variables, functions, conditionals, arrays, loops
  • APIs - fetch(), async/await, JSON, error handling, API protection
  • Deployment - GitHub Pages, Vercel, Render
  • AI-Powered Development - GitHub Copilot, Claude Code, ChatGPT/Claude

You've gone from zero to deploying real web applications. That's significant.

Same AI, Different Results

AI can generate a full website/app from a single prompt. What did you actually learn?

The dreamer asks AI to make brisket:

"I want brisket that's tender, smoky, like the kind you get in Texas."

AI makes it. The dreamer takes a bite: "It's dry... or maybe tough? I don't know, it's just not right. Can you try again?"

You tell AI how to make brisket:

"12-pound USDA Choice whole packer. Trim fat cap to 1/4 inch. Dry rub: coarse pepper and kosher salt, 50/50. Smoke with post oak at 250°F. Wrap in butcher paper at 165°F internal. Pull at 203°F when the probe slides in like butter. Rest one hour."

When It Goes Wrong

The dreamer says:

"It's dry. Try again."

  • They can't tell if it's the wrap timing, the temperature, or the rest time.
  • They just keep saying "try again" and AI guesses from scratch every time.

You say:

"The flat is dry but the point is perfect. You probed only one spot. The point hit 203°F while the flat was already past 207°F. Next time, probe both pieces independently."

  • One sentence. Root cause identified. That's debugging.

How You Think Now

The dreamer says "not right, start over" and AI throws out the whole brisket every time.

You break it into stages:

  • Trim, rub, smoke, wrap, rest - confirm each step before moving on (modular thinking)
  • Test on a small piece first with the same parameters (testing)
  • Write down the rub recipe and temp curve so you can roll back if it doesn't work (version control)

This is what you learned this semester. Not syntax. A way of thinking.

Where to Go from Here

Love design and UI? Advanced CSS, React or Vue, Figma, design systems

Love data and logic? Python, databases (SQL, MongoDB), API design

Want the full picture? Pick a stack (MERN, Next.js), build end-to-end projects

At Babson:

  • OIM3600 - Computational Thinking with Python (Python intro)
  • OIM3640 - Data Analytics with Python and AI (intermediate)

Final Thoughts

  1. You have the foundation. HTML, CSS, and JS are what the entire web runs on.
  2. AI makes you faster, not replaceable. You proved that this semester.
  3. Keep building. The best way to learn is by shipping projects.
  4. Pick one direction. Don't try to learn everything at once.
  5. Stay curious. Tools change every year. Fundamentals don't.

What ultimately matters in this course is not so much where you end up relative to your classmates, but where you end up relative to yourself when you began.

Before You Leave

Final Checklist

  • [ ] Make sure your Final Project is deployed and working
  • [ ] Write your last learning log (wk14.md)
    • What did you see at Demo Day that impressed you?
    • What are you most proud of building this semester?
  • [ ] Final submission due 5/1 (Thu): code, README, deployed URL
  • [ ] Make sure your GitHub profile showcases your work

Thank you for a great semester!

Talking points for this section: - The skill isn't writing code anymore. It's knowing what to ask for, evaluating what you get back, and iterating until it's right. - You can now prototype any idea. Before this class, a "website idea" was just words. Now you can ship it in a weekend. - Technical literacy is leverage. Whether you're managing a product, pitching a startup, or hiring developers, you now understand what's actually happening under the hood. - The tools will keep changing. The mental models you built (how the web works, how data flows, how to debug) won't. - The question isn't "can AI do this for me?" It's "what can I build now that I couldn't before?"