Tietoevry · 90 minutes · everything that was on screen

Vibe coding: salvation,
or a road to hell?

Every example from the session, each one with the full prompt and the reason for each part of it.

vibe-coding.ovacode.cz · one address for everything

Start here

The room's two documents.

The deck

The slides, as they ran

Forty slides, arrow keys to move. Every demo opens from inside it.

 Presenter notes

What was said over each one

The script behind the slides — what each example was there to prove.

Track 1 · anyone

Three small apps. Each one carries a meaning.

The clock — big numbers, a red minute hand, an exercise underneath
on screen at 0:08

The clock

A school lesson: one page that teaches a child to read the time.

Open The prompt
Cat vs Boxes — a cat with a pink collar waits on a pale blue field by the start button
on screen at 0:08

Cat vs Boxes

A game in minutes — the small end of the same idea Craftik and Teriland grew into.

Open The prompt
Who signed up — 394 registered inside a red brush-stroke ring
on screen at 0:08 and 0:12

Who signed up

A dashboard built from a plain list of registrations.

Open The prompt

Track 2 · IT professionals

Nobody watches a one-hour recording. Everyone reads one page.

The meeting minutes — a real architecture call as one quiet page, topics on a rail, every name gone
on screen at 0:24

The meeting minutes

A real architecture call turned into one page. Every name removed.

Open prompt view in progress
The vacation prototype — employee, manager and HR views of the same request
on screen at 0:24, the prompt at 0:30

The vacation prototype

A requirement you can click: four sentences became three roles and four states.

Open prompt view in progress
Planning poker — the live site's door: sign in to run a session, or join one to vote
on screen at 0:37

Planning poker

Where the single file ends: people on different phones sharing one state need a server.

Open the local copy prompt view in progress

Track 3 · engineers

Four pull requests, all tests green. Which one would you approve?

orders-service · four diffs
on screen at 0:45, then 0:47–0:53

The bomb viewer

Four pull requests an agent wrote against a real C# service. Every problem in them is one met in code somebody was paid to write.

Open prompt view in progress
tell · give · enforce · check
on screen at 0:59 and 1:03

The harness

The four layers, weakest to strongest — and the six bombs held against each of them.

Open Six bombs, four layers

The recorded runs

What the agent actually did, keystroke by keystroke.

0:17

Attendance dashboard

Monday 21 September, 09:41 — a list of registrations becomes a dashboard.

0:33

Vacation request prototype

Sunday 20 September, 16:12 — four sentences become something you can click.

1:06

The left-hand agent · no harness

Monday 21 September, 08:15 — the same task with nothing holding it. You can win a lottery; you cannot plan a product on it.

The screen captures were shown from the machine in the room and are not published here. Each run still reads in full as its transcript.

Live elsewhere

Three that outgrew a single file. These open on their own sites.

0:00

Craftik

A voxel world — the same idea as Cat vs Boxes, grown up.

https://craftik.up.railway.app

0:00

Teriland

Six islands in the clouds.

https://teriland.ovacode.cz

0:37

Planning poker

The live version, with the server the local copy does not have.

https://planning.ovacode.cz