MYP Design Vibe Coding Unit Reflection

I got a little behind on my grading, and I can see the issue now, and I will try not to make the same mistake next year.

This year, I allowed students to redo assignments after I graded them. I did not put any constraints on it; I just said anything. As a result, I had a hard time motivating students. 

I started the second semester with a unit in Vibe Coding. This was an assignment that I thought of based on a conversation with a friend and a podcast episode I had just heard. I had intended it to be a way to improve the students' AI skills. 

We did include a checklist at the top of the assignment, 

• I followed my specifications
• I made an adequate prompt
• I made additional prompts
• I did some actual coding
• I looked up code to solve an issue

The checklist was good for the students for sure. But for next time:

• It would be good if the students talked about the prompts with other students,
• It is necessary to ask the students to write the prompts they used,
• We should have had a lesson or two about prompting, but we were time constrained. Next time I would build that in.

Reflection

• The prompt was the most technical part of this criteria. 
• I need to be clear on the outcomes beforehand. That is what really got me. This unit was put together too quickly and next year I will watch for that.

Vibe Coding a Professional Development List

That title doesn't make much sense, but here's the scenario: in my first year teaching, a wise mentor teacher suggested I started writing down all the professional development I took. So, I started a Google Doc with a few columns and started adding to them. It's funny to look back and see that the first ones I attended were freebies put on by my school at the time. 

Thomas Hammerlund Professional Learning and Professional Development

I still think this is good practice for new teachers. (In fact, this might also be a good way for teachers to be introduced to AI.)

https://script.google.com/macros/s/AKfycbxuN0xhABzp0Vdb_4a8GG8HZnme2BlZRw7hCAkYh6VC/dev

Vibe Coding with Claude

Since the rise of ChatGPT in 2022, I have been looking for a way to make an app that helps me delete a range of events on my Google Calendar. 

Right away, I was able to get a Google Apps script out of ChatGPT, but I could not figure out how to get the interface right. So, I put the idea on the shelf.

image via vecteezy.com

This year in MYP Design, I tried a unit about Vibe Coding. 

I was hoping that I could accomplish a few things with this unit. 

1. I wanted students to have a chance to use AI tools if they had not yet tried them. 
2. I wanted students to see both the benefits and the limitations of AI.
3. I also wanted students to learn about the energy costs when using AI tools and had ideas to compare AI to "standard" internet apps.

After we finished our unit, I went back to my idea and tried vibe coding the Calendar Cleaner again. 

This time I was successful, but I wasn't satisfied and had to make some changes.

1. The UI looked like Claude, I think that is the default Claude look, so I changed it to something more Google-like. 
2. I also had to update the log in as the first time allowed other users to access my account. (!)
3. I added a help page.
4. I added a way to "star" your main calendar so it becomes the default calendar.
5. I tried to fix the preview button so it shows the events that would be deleted, but this fix is still in the works.

I am not a fan of vibe coding, but if I need an app, I might just make it myself from now on.

Give Calendar Cleaner a try here.

(The updated name is Google Calendar Cleaner.)