The AI Teacher Lounge

Hey everyone, Scott here, with Digi-Ford helping me sort through the pile.

This week’s theme is pretty simple: AI and technology keep getting easier to use, but easier does not automatically mean better.

That is not a grumpy old teacher take. That is just classroom reality.

A tool can be impressive in a demo and still fall apart when thirty students are using it on mixed devices, the Wi-Fi is acting weird, and someone forgot their password for the third time this week. Ask me how I know.

So this week, we are looking at a few stories that all circle around the same idea: the tool is not the whole lesson. The human judgment around the tool is still the adult in the room.

Grab your coffee. Here are a few things worth knowing.

Source: eSchool News
Link: https://www.eschoolnews.com/innovative-teaching/2026/06/01/this-districts-stem-space-station-is-a-growing-youtube-hit/

What happened: Duval County Public Schools helped create Spacegate Station, a fictional STEM-focused space station used to support science and technology learning. It has grown beyond a simple local resource and picked up attention through YouTube and online lessons.

Why educators should care: This one is not really an “AI story,” and that is actually part of why I like it. Not every useful technology idea needs to start with artificial intelligence. Sometimes the win is using story, video, characters, and a clear instructional hook to make students care about the topic.

That matters because AI tools are going to make video, audio, scripts, simulations, and classroom media easier to create. But the lesson here is not “go make a fake space station by Friday.” Please do not do that to yourself.

The lesson is that students often connect with content better when it has a world, a purpose, and a reason to keep paying attention.

What to watch: As AI media tools get easier, teachers may be able to create more story-driven lessons, quick scenario videos, or fictional workplace simulations. The caution is that the story still needs to serve the learning. Otherwise, we are just adding a cape and a sound effect to a worksheet.

Source: Tech & Learning
Link: https://www.techlearning.com/technology/ai/4-strategies-for-teaching-with-ai-effectively

What happened: Tech & Learning highlighted advice from University of Central Florida professor Humberto López Castillo, who encourages thoughtful AI use with students while still requiring critical thinking, personal input, and human review.

Why educators should care: This is one of the better AI classroom messages because it does not live in the two unhelpful extremes.

Extreme one: ban everything and pretend students are not using AI.

Extreme two: let AI do whatever it wants because “the future.”

Neither one is a great plan.

The useful middle ground is setting clear expectations. When can students use AI? What do they have to disclose? What part of the work still has to be theirs? How will they check what AI gives them?

Those questions matter more than the specific tool.

What to watch: The big takeaway is that AI use needs structure. “You may use AI” is not a policy. It is barely a sentence. Students need examples of acceptable use, unacceptable use, and what human effort looks like after AI has helped.

Source: EdTech Magazine K-12
Link: https://edtechmagazine.com/k12/article/2026/05/k-12-data-analytics-turning-district-data-student-success-perfcon

What happened: EdTech Magazine covered how K-12 districts are trying to connect scattered data from attendance, assessments, behavior, grades, and other systems so educators can spot patterns and respond sooner.

Why educators should care: Schools are not short on data. They are short on usable data.

Most teachers do not need fifteen dashboards, twelve exports, and a login scavenger hunt. They need answers to practical questions: Who is falling behind? Who has stopped showing up consistently? Which lesson or unit is not landing? Which students need support before the problem becomes a full-blown rescue mission?

This is where AI and data tools could eventually help, but only if the information is accurate, understandable, and tied to real decisions.

What to watch: Better dashboards can help, but they are not magic. Districts still need clean data, training, good questions, and trust. A pretty chart with bad data is still bad data. It just dressed up for the meeting.

Source: Tech & Learning
Link: https://www.techlearning.com/technology/ai/what-is-vibe-coding-creating-code-with-ai-explained

Google AI Studio’s vibe coding features are worth watching, especially for computer science, STEM, CTE, and digital literacy teachers.

In plain English, vibe coding means you describe the app or tool you want, and AI helps generate the code. Instead of starting with every line of syntax, the user starts with the goal: “Build me a simple quiz app,” “Make a flashcard tool,” or “Create a small game for reviewing vocabulary.”

That can feel pretty magical.

It can also be a mess.

The Tech & Learning article makes an important point: vibe coding is not just pushing a button and receiving a finished, trustworthy app. The user still has to test it, question it, revise it, and understand whether it actually works.

Who it might help: Teachers who want quick prototypes, students learning how software logic works, and CTE programs looking for low-barrier ways to explore app ideas.

The caution: I would not trust a vibe-coded tool with sensitive student data, grades, or anything mission-critical without serious review. For classroom prototypes, demonstrations, and “let’s see if we can build the idea” activities, though, this is one to watch.

My take: promising, but best used as a learning tool before it becomes an operational tool.

Here is a simple one you can try without rebuilding your whole class around AI.

Pick a topic you are already teaching. Ask AI to generate a short explanation, summary, example, or set of directions related to that topic. Then give the AI output to students and ask them to critique it.

Their job is not just to say, “This is good” or “This is bad.”

Give them a short checklist:

• What is accurate?
• What is confusing?
• What is missing?
• What needs a better example?
• What would you rewrite for a younger student?
• What should the teacher double-check before using this?

This works in almost any subject.

In science, students can critique an explanation of photosynthesis.

In history, they can check a summary of an event.

In English, they can improve a paragraph.

In computer classes, they can test AI-generated instructions or pseudocode.

In CTE, they can review a workplace scenario or procedure.

The point is not to make AI the expert. The point is to make students practice judgment.

That is the part we need more of.

AI can produce text quickly. Students still need to learn how to inspect it, challenge it, improve it, and decide whether it is worth using. That is a real skill, and it is going to matter more, not less.

I keep coming back to this idea: AI is making the first draft easier.

That is true for writing. It is true for coding. It is true for lesson ideas. It is true for emails, rubrics, examples, summaries, and probably three things I have not thought of yet because I have not had enough coffee.

But the first draft has never been the same thing as finished work.

Teachers know this. We have seen enough student work to know the difference between “I started” and “I am done.” Sometimes that difference is a canyon with a Chromebook cart parked at the bottom.

That is where I think AI gets interesting in education. Not because it replaces thinking, but because it gives us something to think about faster.

A student can generate an explanation, but can they tell if it is accurate?

A teacher can generate directions, but are they clear enough for actual students?

A district can generate a dashboard, but does it help anyone make a better decision?

A coding tool can generate an app, but does it work after someone clicks the wrong button?

That is the classroom conversation.

I do not think the winning move is pretending AI does not exist. I also do not think the winning move is tossing every shiny tool into the classroom like Oprah handing out cars.

“You get an AI tool! You get an AI tool! Everybody gets an AI tool!”

That sounds fun until someone has to manage the logins, permissions, privacy settings, broken outputs, and parent questions.

The better move is slower and more practical. Use AI where it reduces friction. Teach students how to question it. Keep the human judgment visible. And do not confuse faster output with deeper learning.

AI can help. Sometimes it can help a lot.

But the teacher still knows the students. The teacher still knows the goal. The teacher still knows when something looks good on the screen but will fall apart in period three.

That is not a weakness in the system.

That is the system working.

This week in StackFord, I have been thinking a lot about the “AI plus human review” workflow.

That is not just a newsletter idea. It is becoming part of how I think about curriculum, labs, simulations, teacher support, and student work.

For example, when students use AI to create an answer, the learning cannot stop there. The better assignment is asking them to explain what they changed, what they rejected, what they verified, and where the AI needed help.

That same idea applies to teachers. AI can help draft directions, build examples, generate review questions, or outline a lesson. But the teacher still has to make sure it fits the class, the timing, the reading level, and the actual learning goal.

The bigger takeaway: AI should not remove the thinking. It should move more of our time toward the thinking that matters.

That is the sweet spot I am trying to build toward.

Digi-Ford does the digging. Scott does the thinking.

That is the model I want students and teachers to see with AI. Let the tool help, but do not hand it the steering wheel and climb into the back seat.

See you next week.

Scott
The AI Teacher Lounge