Skip to content
zerotheoryAI
All field notes

How to start coding when you know absolutely nothing

A practical first path through files, browsers, HTML, JavaScript, and your first working project. No technical background needed.

Start with something you can see

Your first goal is small: change something on a screen and understand why it changed. A personal webpage is a useful starting point because you can edit a heading, save the file, and see the result immediately. You do not need to choose a career specialty or install ten tools first.

Learn what the three web languages do

HTML describes the content: headings, paragraphs, links, and buttons. CSS controls presentation: spacing, color, layout, and how a page fits a phone. JavaScript adds behavior: a button can update a counter, a form can check an input, and a page can request data. Learn them in that order, using the same small project.

Your first exercise

Create a file named index.html. Add a heading with your name and a paragraph describing something you want to build. Open the file in a browser. Change the heading, save, and refresh. Next, add a link to a website you use. You have now completed the edit, run, observe loop that underlies programming.

<!doctype html>
<html lang="en">
  <head><meta charset="utf-8"><title>My first page</title></head>
  <body>
    <h1>Hello, I am a builder.</h1>
    <p>I am learning to make useful things.</p>
  </body>
</html>

Use errors as information

When something breaks, write down what you expected and what happened instead. Read the first relevant error, check the file and line, and change one thing at a time. Copying a large replacement from AI can hide the original mistake. Ask for an explanation and a small fix, then test the result yourself.

Build a habit you can keep

Try a short daily practice session: review yesterday’s work, add one change, and explain it in your own words. Keep the scope small enough to finish. A working page with three features teaches more than an ambitious app you cannot yet run. After the basics, learn Git so you can save and compare versions.

How to know you are making progress

Can you change the page without following every click in a video? Can you explain what a line does? Can you find and fix a mistake you introduced on purpose? These are better early signals than hours watched. Keep a folder of small projects and a note about what you learned from each.

Keep exploring

Use AI to write code you actually understand

Your first developer portfolio needs proof, not polish