Code with Intention

You now know the principle. Code is thought in machine language. AI can translate. But how do you use this for something that really benefits you?

The Magic Lies in the Description, Not the Code

Here's the key: Many people think good code is the goal. Wrong. The goal is that your problem gets solved. The code is just the means.

That's why the best prompting for code is not technical. It's human. The better you can describe what you need, the better the code will be.

Example:

Weak prompt: "Write a Python script that reads JSON" Strong prompt: "I have a JSON file with customer data (name, email, purchase date). I want a simple list showing: [Name] bought on [Date]. Only purchases from this month."

See the difference? The weak prompt is technical. The strong prompt describes YOUR INTENTION. What do you want to see at the end?

Three Scenarios: From Practical to Creative

Let's look at three scenarios where you can use AI for code.

Scenario 1: A Personal Website

This is the simplest. You want a website where visitors learn more about you.

Weak prompt: "Create a website"

Strong prompt: "I want a simple website for my photography work. At the top should be a large photo of me, then three sections: Portfolio (with 6 images), About Me (short text), Contact (email form). The colors should be warm, earthy tones. The text should be in English. The design should be modern and minimal — little text, lots of space."

The strong prompt works because it makes clear: what's the website for? Who should see it? What's the tone? What colors? AI can work with concrete images.

Scenario 2: A Data Script

You have a file with information you want to process.

Weak prompt: "Write a script that converts CSV to table"

Strong prompt: "I have a CSV file with my monthly expenses (date, category, amount). I want a Python script that: 1) reads the file, 2) calculates sums per category, 3) outputs the result in a nice table, with the biggest category at the top. Can it also show what percentage each category is of the total?"

Again: Your intention is clear. AI knows what you need.

Scenario 3: An Automation Tool

This is harder — but possible.

Weak prompt: "Create a script that automates files"

Strong prompt: "I save photos from my camera to a folder every month. I want a script that: 1) goes through all photos, 2) renames them by date (e.g., '2024-02-15-001.jpg'), 3) organizes them in folders by month ('2024-02', '2024-03', etc.), 4) deletes duplicates (if the same file is there twice). I'll take Python or Bash, whichever is easier."

This scenario shows: even with complex tasks it works when you make clear which STEPS you need.

The Checklist Approach

Here's a simple method to write good prompts:

1. What's the end goal? (not: "write code," but: "I want my photos organized automatically")

2. What's the input? (Files? Text? A form?)

3. What's the output? (A table? A website? A folder with sorted files?)

4. What are the steps? (read file → process → save)

5. Are there special cases? (Only photos from this month? Only if amount > $50?)

With these five questions you have a complete brief for AI.

The Meta-Lesson: It's Not About Code

Here's the most important thing you should take from this entire cluster: Code is not the goal. Solution is the goal.

In K01 we learned that text can be made by AI. In K02 music. In K03 images. In K04 video. In K05 code.

The common element is not the technology. The common element is intention. With each of these tools you've learned that your idea matters more than the technique. The clearer your idea, the better the result.

This is not a course about code. This is a course about how to use your brain — and AI as a tool — to make ideas real.

You don't need to be a programmer. You just need to know what you want. The rest is communication.