Why My College Kid’s Programming Professor Requires AI (And What It Means For Parents)
The pasta was still warm on my son Leo’s plate when he dropped his crumpled syllabus on the dinner table last month. “You’re gonna think this is crazy,” he said, pushing a stray hair out of his face. “My new programming professor says we have to use AI for our midterm project. If I write every single line from scratch, I lose points.” My golden retriever nudged my hand for a bite of garlic bread, and I froze. Back when I was in college, turning in any code you didn’t write yourself would get you kicked out of the class for cheating. This felt wrong, plain and simple.
I almost pulled up the department contact page that night to send a confused email. But Leo sighed and said I should just read the assignment fine print before I overreact. So I did. The project was to build a custom to-do app for college student groups. The requirements didn’t say “let AI write your whole project.” They said: generate the basic boilerplate code (the repetitive navigation, login screen, and database setup that every app needs) with an AI tool of your choice. Then, modify the code to add custom features, debug every error the AI made, and write a line-by-line explanation of every change you made. That’s 70% of your grade, the syllabus said. The final working app is only 30%.
I asked Leo what that actually looked like for him day to day. He said for his last project, with a different professor who didn’t allow AI, he spent three full days just writing the basic login and navigation code. It worked, but by the time he got to the part of the project that tested actual learning—building custom permission settings for different group members—he ran out of time and turned in a half-finished version. He got a B. This time around, AI wrote that base code in 10 minutes. He spent those three days tweaking the permission settings, adding screen reader accessibility that the prof had asked for, and testing the app with three of his dorm friends who have low vision. That’s the part he said actually taught him something he’d use later.
A week later, I went to my son’s university parent weekend for comp sci majors, and I pulled the department advisor aside to ask about this. I wasn’t complaining, just curious. She told me this shift happened two years ago, and most incoming freshmen’s parents ask the same question I did. She said ten years ago, profs encouraged students to search Stack Overflow for existing code snippets to build their projects. Before that, it was copying code out of textbooks. AI is just the next step. Every entry-level programming job right now expects new hires to use AI to cut down on repetitive work. If they graduate and can’t tell good AI output from bad, or can’t fix AI’s mistakes, they won’t get hired.
After that conversation, I started thinking about what I’d tell another parent in my spot who’s confused or worried by this new requirement. First, don’t panic before you read the actual assignment requirements. Most of the time, when profs require AI, they’re not cutting corners. They’re changing what they test. Instead of testing how well you can memorize syntax and write repetitive code, they’re testing how well you can review, edit, and improve AI output—which is the skill people actually use on the job now. That’s a huge shift from when we went to school, but it’s not a reckless one.
Second, if your kid is confused about what counts as acceptable use, tell them to book a 10-minute office hour meeting with their prof to see a sample of good work. Leo did that, and he brought back a printed sample assignment where the prof had marked up exactly what worked: AI writes the base, you add comments explaining every line, you change anything that doesn’t fit your project’s goal. That’s way clearer than trying to guess from the syllabus, and most profs who require AI are happy to walk through it—they know it’s new for students too.
Third, if you’re a parent of a high school kid looking at comp sci programs, don’t cross off programs that integrate AI into coursework. Instead, ask one simple question when you tour: do they grade students on their understanding of the code, or just the final product? If the answer is understanding, it’s not cheating—it’s training.
I still have small doubts, honestly. Last week I asked Leo if he can still write a basic login page from scratch, without AI. He said yeah, he did that for his first-year classes, and he can do it again if he needs to. Now he just doesn’t have to waste time doing it every single project. That makes sense. I remember when my high school math teacher got in trouble for letting us use calculators in the 1980s. Everyone said kids would forget how to do long division. Now we all use calculators, and we still learn long division in elementary school. This feels the same way.
Last weekend, Leo sent me a screenshot of his midterm grade. He got an A, and the prof’s note at the bottom said “Great work catching AI’s flawed permission logic—this is exactly what we want to see.” I still don’t know what flawed permission logic is, and I probably never will. I’m still getting used to the idea that the rules I learned for school don’t apply anymore. I don’t think this shift is perfect, and I’m sure there are still kinks to work out as more profs adopt it. But for right now, Leo’s getting good grades, he’s talking about his interviews for summer internships, and every interviewer he’s met has already asked him to walk through how he uses AI in his work. It’s weird, it’s new, but it’s not cheating. It’s just preparing kids for the world they’re going to work in, not the one I grew up in. I’m okay with that, for now.
Please indicate: Thinking In Educating » Why My College Kid’s Programming Professor Requires AI (And What It Means For Parents)