Tietoevry Tech Talks · Webinar roster

Vibe Coding —
Salvation or
Road to Hell?

Three hundred and ninety-four colleagues put their name down. Before the first line of code, here is the room: where it sits, who is in it, and what it does for a living. Four quiet pages, then everything at once.

394 people registered 394 registered

One · Places

The room has
a geography.

people whose org unit names a country or a delivery region
the largest single location

Location is read from the organisational unit — the only geographic signal the roster carries. Product organisations don't encode one, so people stay unplaced. Hollow rings are delivery regions rather than countries.

One dot, one person — hover a block or a name.
Each dot is one registrant, grouped by location

Two · People

Roughly one
in four and a half.

women registered, of 394 — of the room

Gender is not in the roster. It is inferred from first names against a hand-checked dictionary; names that carry no reliable signal are reported as undetermined rather than guessed.

394 dots, one per registrant, coloured by inferred gender

Three · Craft

What the room
does all day.

Registrants by functional area

Functional area is derived from keywords in the organisational unit — the roster has no job-title column. Hover or tap a bar to open it up.

Four · Everything at once

The whole room.

Filter Click anything below — the other panels follow.
Where
What they do
Who
Busiest teams

Every figure on these pages is derived from a six-column registration export — last name, first name, user ID, organisational unit, e-mail, status. Country, gender and function are inferences, not fields. Treat them as a good read of the room, not as a personnel record.

One prompt, six parts

the same six parts — the room this time step · 06 jump · D the dashboard

What I asked for

What I got — scroll it

What changed