Computer Science in the AI Era

If you still have your code editor installed, and even worse, if you're still prompting an LLM one request at a time like some kind of caveman, you're going to get left behind as a software engineer. What you want to be doing is designing loops. So, instead of asking the AI to build a feature, you write a

loop that asks the AI for you. And then you take a second AI and you tell it to act as an AI supervisor with 10 years of experience. So, when the first AI writes the code, the supervisor reviews it and tells it what to fix and what [music] to do next. And then, ideally, that whole

thing runs on a schedule overnight while you're asleep. So, all you need to do is wake up and talk to the manager without ever even seeing a line of code. You're not really a programmer at this point. You've ascended into a loop engineer. Okay, I'm just kidding. If you're watching this, I'm guessing you're not

running an autonomous code factory while you sleep. You're probably someone who actually wants to get good at this. If that's you, then using the most abstracted hands-off 10 AI agents form of coding is probably not the best way to learn how to code. So, I want to talk about how to actually code with AI

without completely losing your brain. Okay, every time you sit down to build something, you're in one of two modes. Either you're [music] trying to ship and you just want the thing to exist, and you don't really care how it gets done, or you're trying to learn, where the whole point is that you come out the

other side better than you went in. And both of these are completely fine, as long as you're honest about what you're actually doing. The issue is when you think you're learning, but every time you code, you're using AI to write the entire thing, and then you skim it, watch it run, and then you feel