No script “just a small one”. Another course, other crafts.
When Maker is surprised, people want “let AI write it in HTML, so the poster blinks”. That is 发明家 and a programming course. Here you turn in a question, a check, a sign, a slogan, five slides. Code from a model does not belong here, even when it is short. Even when “only for a school website”. A school website has an admin and rules. Pasting a generated script you do not get can break a page or make a hole. It is not heroism. It is another game. Today you practise refusal: when a model pours code, stop. When you ask for code, cross out the prompt. A bridge: you can describe what a poster should do in human words. Doing it in code another level of another course teaches.
Bára writes “make a campaign website”. HTML pours. Adam: “Wrong door.” Bára: “five slogans and a script, no code.” It works. An ICT teacher would want code so Bára could explain it. Here she cannot. Pasting would be a bundle like at translation. You do not get it, you do not hand it in. Bára writes on the Maker margin: no code marks. When she sees code brackets, a mix-up drawer — rephrase into slogans. It is not fear of code. It is respect for a course line and for a website that is not your experiment.
If you see code marks in an answer, do not copy them onto a school page. 关闭. Another prompt. Or another course.
A user, a builder, a website admin
A user: you here. A builder: 发明家 / a website builder. An admin: school, a parent, Martin’s hosting — not you with a dump. A request for code is a mix-up of a role. A fix: a human output. When you want to build, go to that course honestly, with an account and lessons. Mixing gives a fake feeling that Maker is a junior programmer. It is not. It is a junior of making ethics. That is enough work. Code would only mask that work with blinking. Blinking with no honour is carnival again.
A bad prompt: “Write an HTML poster with a button.” A good one: “Suggest a poster layout in words: a slogan at the top, 3 rules in the middle, a sign at the bottom. No code.”
When code comes: “Stop, no code. Only words and a list of poster parts.”
A door table:
| You want | A door |
|---|---|
| a slogan, a sign, 5 slides | Maker |
| a chatbot on a website, HTML, a server | 发明家 |
| paste a script onto a school website | an admin, not you blindly |
Do not copy code you do not get “just so it works”. Working can also be wrong. 学校 does not want to try that from your USB.
Why this right now
You are in the course Ask with Martin, level Maker. You work in a chatbot (ChatGPT, Gemini or Claude) — same game, different brand. No code. A parent or the school creates the account. A child’s email does not belong here.
This is not the 发明家 level. There you build a chatbot on your own website. Here you are a user: a question, a check, a citation.
You will know this lesson by one sentence: In this course you are a user. Code belongs in 发明家, not in a poster from chat. When you can say it to a parent or a teacher, you have got the core. The rest is practice, not magic.
You can do a play with words. Code would skip it with blinking. Tomorrow a shared class prompt — still words, not a script on the board.
Four things you will build in this course
The course has four small projects. You do not have to do them all at once. Today you add only what this lesson can do.
🏫 A report with citations
An outline, three sources that exist, and a sentence in your own words. AI must not be the only author.
A campaign is paper and speech, not a website from a dump.
📝 Test training
Coach role: let it ask, do not let it say the answer. You count / answer yourself.
A report does not contain code.
📅 Family planner
Tasks for the week (not passwords, not marks). A parent sees the plan, not your chat.
A planner is a table, not an app from AI.
📜 An AI code for the class
Seven short rules on a poster. No horror — a how-to.
Code: an 发明家 line on a poster as a sentence.
Workshop: a human sketch of a poster
Describe a poster in words and boxes on paper. When the window pours code, send it back. The goal is a sketch, not a .html file.
-
On paper three boxes: a slogan, rules, a sign. By hand.
-
M1: describe the same in words, a ban on code. When code, a stop move.
-
Compare paper and words. Paper wins as a hand.
-
Do not copy anything into a website editor.
-
A trail: a user, not a builder. 发明家 another time.
Practice: which door
Maker, 发明家, or an admin?
-
Five slogans on paper.
-
HTML from chat onto a school website.
-
Your own chatbot on a page.
Now you 💪
Go through three checks. At each one tick in your head: can I see it, or not?
- You did not copy code onto a school place.
- You can rephrase into words.
- You know where 发明家 starts.
If something is missing, go back to the steps above. This is not a test for marks. It is a safety net, so you go on sure, not confused.
Check: A poster lives in boxes on paper. A script stayed behind the door of another course.
What to take from this lesson
- A user ≠ a builder.
- Code does not belong here.
- You do not get it → you do not hand in a script.
- Blinking does not mask honour.
- 发明家 is another chain of lessons.
- The names in the examples (Bára, Adam) are made up. Do not put your number, email or photo here.
- Next lesson: When you can do this, go to the next lesson in the same level.
© 2026 Ing. Martin Polak / AlgoRhino · 内容使用条款