BiUH · Computer Science · 3rd Semester · Autumn 2026
What this field is · how the course runs · how you are assessed
Before anything else
Every slide, every session, every lesson in this course lives at this address. Bookmark it.
These slides are there too — you can follow on your own screen, and read them again tonight.
What this deck covers
| The field | what this actually is |
| The semester | eight days, nine weeks |
| The tools | why you write it by hand first |
| The project | a website of your choosing |
| The assessment | what is marked |
Full course material at webtech.landrock.io/course
The semester
| 1–3 | How the web works — by hand |
| 4 | Layout — and the AI agent arrives |
| 5–6 | Behaviour and composition |
| 7–8 | The project, then its presentation |
Plus two self-study Saturdays. Each day is one unit with a beginning and an end.
One thing to say up front
At first you write
everything yourself.
Later in the course an AI agent writes alongside you, and then it stays. The reason for the wait is simple: you will have to judge whether what it gives you is correct — and you can only do that if you have done it yourself first.
Your project · the whole course
What it is, is up to you. A portfolio. A site about something you know a lot about. A shop, a tool, a guide, something for your family or your band.
At least four pages, your own content, live at a real address by November — and you will demonstrate it and answer questions about your decisions.
You choose in session 3. Until then we practise on a shared exercise.
How you are assessed
| Weight | Component | What it assesses |
|---|---|---|
| 20% | Process | your project growing, in your Git history |
| 40% | Project | the finished site, live |
| 25% | Written exam | reading code and finding what is wrong |
| 15% | Project presentation | presenting it, and defending your own decisions |
No exam question will ask you to
write an HTML form from memory.
A machine can do that. What is assessed is whether you can read code, find what is wrong with it, decide where a problem lives, and justify what you built.
The shape above is settled even if the numbers are not: a project, a written exam, and a project presentation. And twenty commits in one evening in November is not a process — the Git history is the one part that cannot be made the night before.
The question I get asked every year
It is not marked. It is not recorded. It will not appear anywhere in your grade.
Attendance is not the point.
Attention is.
Which is a bigger ask, not a smaller one.
Sitting in this room for six hours with your phone in your hand teaches you nothing — and it costs you the day anyway.
If that is where you are,
we are both better off if you take a break and go.
No hard feelings, and no consequence. Come back when you can actually be here.
Why I mean this literally
One hour of real attention beats a full day of being present. The work you produce is the only thing that gets marked — and that work comes from the hours you were really here.
Today
| Now | where we are going, and why |
| Morning | where files live · how a page reaches you |
| Afternoon 1 | your first page, by hand |
| Afternoon 2 | style it · break it · fix it |
| Afternoon 3 | your working environment |
Ready
| Lesson 1 | Web Fundamentals — how the web works, DevTools, HTTP |
| Lesson 2 | HTML — structure, links, images, forms, semantics |
Both are on the site, as slides and as full lessons.