Thinking
Vibe Coding Still Needs a Person Who Can Read
A sentence can produce a program. It does not produce someone who can explain what that program will break.
People call the shortcut vibe coding. You say what you want. A tool writes the file. The name is the warning. A vibe is not a reading.
-
You asked
A sentence. That is the request, not the review.
-
You read it
Inputs, output, and anything the program sends or deletes.
-
You can say
What it will break. One bug you would notice is the minimum.
The standard on this site
Section titled “The standard on this site”The Python course and the marks book are small on purpose. You can run them. You can say what the 50 means, and that it is not a CSEC grade. A program you have not read cannot meet that standard, however fluent the sentence was that produced it.
Read three things:
- What goes in, and what comes out.
- Anything it sends off the machine, or saves, or deletes.
- The branch you did not try. The happy path is not the program.
If you cannot name one bug you would notice, you are not ready to let anyone else rely on it. A weekend can hold a draft. It does not hold a product.
Try it
Read this before you accept it
Say what it does, on this page. Nothing is sent, and the program is not run.
price = input("Price: ")
tax = price * 0.125
print("You pay", price + tax) A reading
input()returns text, including when the person types digits.- The second line multiplies that text by 0.125. In Python 3 that raises TypeError. It does not compute a tax.
- Any price does that, including 10, and so does a blank line. Nothing in the program turns the text into a number.
Compare that with what you wrote. This page does not mark your sentences, and it does not ask a chatbot to.
What you do not paste in order to get the reading
Section titled “What you do not paste in order to get the reading”A client’s code, a password, a private repository, a spreadsheet of real people. Describe the shape. “It totals a list and compares each item with a pass mark.” That is enough to talk about the idea. The file stays where it is. The rule is what never to paste.
The test
Section titled “The test”Close the tool. Say, to a blank page or to a person, what the program does and what it will get wrong. If you need the thread on the screen to say it, the thinking is still in the tool. That test is the whole of the last piece in this section.
Discussion
View all discussions on GitHub