If code comes out when you describe it, why doesn't it end there? — Coding
Getting the code is just the start; coding begins the moment you run it.
1 · Think first
It's true that if you describe it in words, code comes out. But the real half of coding happens after the code comes out — running it, reading the errors, fixing it.
With AI-written code, nobody knows if it's right until it runs. What decides isn't whether it looks believable, but whether running it gives the result you wanted.
So a red error message isn't you getting scolded — it's a note telling you what went wrong. Showing the whole thing to AI is the fastest way to fix it.
2 · Experiment · Put it in order
Try it — The order it takes to get code running
Tap the mixed-up pieces in order. Whether you're building a game or organizing a homework spreadsheet, this order is the same.
Tap the pieces below in the order you think is right.
Figure
Coding isn't one line, it's a loop
Using AI doesn't make this loop go away. It just goes around faster.
3 · Quiz
Quick check
Three questions. Pick an answer and it's marked right away, with the reason why.
Today in one line
Today in one line
Getting the code is just the start;
coding begins the moment you run it.
Learn more
- The paper that shows how AI-written code got graded — the answer was 'run it and see if it passes' — Evaluating Large Language Models Trained on Code (2021)
- The official announcement from the day a code autocomplete tool opened up to everyone — GitHub Copilot is generally available to all developers (GitHub, 2022)