Pullets Forever

20 Years of Banning Phones. We Don't Have That Long for AI.

David W. Keith

I was on Apple's campus watching a live stream of Steve Jobs presenting his now iconic iPhone Introduction at Macworld 2007.

...a widescreen iPod with touch controls; a revolutionary mobile phone; and a breakthrough Internet communications device. An iPod, a phone, and an Internet communicator. An iPod, a phone... are you getting it?

Steve Jobs

The world changed, the Internet was mobile. We now had the ability to carry a supercomputer in our pockets. Over the years that supercomputer got many sensors: a camera, accelerometer, gyroscope, compass, LiDAR, and more. A device that could have transformed how students learn. Instead, we banned it. And still, almost two decades later, despite many cries to integrate technology into the classroom,* most schools still ban smartphones, turning phones into forbidden fruit, binged after school.

Research from CMU found that students' performance was even better when teachers asked them to use devices to aid instruction—not worse.

Today we have Artificial Intelligence (AI) in the form of Large Language Models (LLMs) from OpenAI, Anthropic, and Google. This school year many school IT departments either blocked or ignored them. Google only allows Gemini in Classroom to be used by students over 18. Effectively banning their own product in K-12. We are already not teaching students how to avoid distractions on their phones, and are already losing a generation to algorithmic distraction. Not integrating AI will cost us another generation of students unprepared for the realities of modern work if we don't teach students emerging best practices as we develop them.

We don't have 20 years to figure out how to integrate AI into the classroom

I co-teach AP Computer Science A, the high school equivalent of CS 101. As such, it is nearly impossible to avoid AI, by definition these students are excited about technology—that's why they signed up. Yes, most are going into other sciences, but all science disciplines are already using AI in one way or another, and that won't change, we've passed the point of no return. AI will be in the offices and labs of the future. We need to prepare students with best practices on how to use it.

The Evidence

Early research shows students learned almost twice as much with AI tutoring compared to in-class active learning. The key to that success? Context. The AI knew what topics students had covered, where they struggled, and what came next. Without that context, AI is just a chatty search engine. With it, you have a tutor. As one researcher put it:

We know what topics they're covering in the next 20 weeks — we know the curriculum. We know the other students in the classroom. We know whether they're putting effort into their questions. We know whether they're watching videos or not — we know so much about the student without passing any personally identifiable information to the AI.

the74million.org

Hallucinations are a real concern—but when working with common educational material, the numbers are encouraging. One study found the supervised AI tutor hallucinated just 0.1% of the time: 5 errors in 3,617 messages. I've been teaching this curriculum for years, and I'm nowhere near that accurate. Just ask my students.

Critics argue we're moving too fast. A widely-cited Wharton study found that high school students given access to standard ChatGPT performed 17% worse on exams than students with no AI access—what researchers called using AI as a "crutch." Some professors report a "junior-year wall" where CS students who coasted through intro courses with AI can't handle advanced work without it.

But read the Wharton study closely: students using a tutor with pedagogical guardrails—one designed to guide rather than answer—showed no negative effect on learning. The problem isn't AI in education. It's unguided AI. ChatGPT is designed to be helpful, which in an educational context means giving away the answer. A well-designed tutor does the opposite.

The "junior-year wall" critique assumes the goal is producing engineers who work without AI. But that's not the job market students are entering. AI fluency is becoming a baseline expectation, not a crutch. The question isn't whether students will use AI—they will. The question is whether they'll know how to use it well.

How to Build One

Claude Chat with AP CS A Tutor project

The project prompt instructions I created are for my class, AP CS A, but the same principles apply to any curriculum. When writing your own instructions, tell the agent to guide, not solve—following evidence-based tutoring practices—as a core principle. Add a "never" section that reminds the AI not to write complete solutions and instead ask probing questions. Tell the agent how to handle pushback when students demand answers, and how to keep frustrated learners engaged. Give examples that anchor the instructions in role playing practice. Basically the same guidance you would give to a new human tutor.

Once you have written a document that describes the ideal tutor for your class, you can export it to Markdown and create a project in your AI of choice. Chats in that project, or gem as Google calls them, will use the instructions as a base-prompt for any new conversation in that project. For the latest LLMs the approach works the same way—pick the platform that fits your school's policies and your comfort level.

With the right tooling, parents and administrators can review every conversation. The tutor keeps logs. This isn't a black box—it's a teaching assistant with a paper trail.

Yes, I'm asking students to use corporate tools. I got into volunteering through TEALS, Microsoft's nonprofit. The class runs on Chromebooks managed by Google Classroom, writing code on code.org—which is powered by AWS. Corporate infrastructure is already the foundation of public CS education. The difference with an AI tutor is we're showing students how the tool works, what it's good at, and where it fails—instead of pretending it's neutral infrastructure.

Why It Works

Now, I know kids are smart. They can game the tutor, they can open a new window, they can use another AI tool. This isn't new. Kids have been copying from peers, older siblings, and parents who think they're helping since school began. AI doesn't change that, it makes 'cheating' faster and more available. We already have solutions for that, in class testing. A student who is not learning won't pass the test, it is obvious. That's an implementation gap for the platforms to solve—not a reason to abandon the approach.

AI also provides a guard against cheating: immediate, personalized feedback—among the most effective influences on learning. Finally an algorithm that is good for us. Once students become motivated learners, the feedback loop snowballs. They have a tireless tutor who adapts to them, knows the curriculum, guides using pedagogical best practices, and is ready to teach 24/7, whenever the student is ready. And AI can democratize access to personalized tutoring at a scale we have never seen before.

To be clear: the tutor doesn't replace me. It handles the 11 PM debugging session so I can focus on the parts of teaching that actually require a human—mentorship, motivation, helping students see the bigger picture, and knowing when a kid is struggling with more than just code. The tutor teaches Java syntax and problem decomposition. I teach everything else.

China made AI education mandatory for six-year-olds this year. We're still deciding whether to block ChatGPT.

Banning AI use in the classroom is as short sighted as banning smartphones. These are tools that students must master, both the positive and negative aspects, in order to survive in modern society. Teaching students to get the technology to work for them, while they are still young and still forming habits gives them skills their future employers will expect them to have.

AI is evolving fast. Best practices are constantly being rewritten—states are publishing guidance as living documents with biannual review cycles. I want to stay on top of what's working. Let me know your ideas. My socials are in the footer.

-dwk


  1. *Proper smartphone use in the classroom is well researched.

  2. In an app like Google Docs or Apple Notes, or write Markdown directly in any plain text editor.

  3. All three major platforms support project-based instructions: