A newcomer track is a set of decisions an event takes about the people who have never been to one before. Some of those decisions are programme decisions, some are logistics, and a few cost nothing at all. Taken together they determine whether somebody attending their first conference spends the day learning things or spends it working out where to stand.
What a newcomer track is, and what it is not
It is not a separate event running in a side room, and the events that build one that way generally regret it. A parallel beginner conference removes newcomers from the main room, which is where the value of attending actually is, and it signals that the real conference is happening somewhere else.
What works is a set of adjustments to the ordinary conference. One or two talks pitched at the first band on the chart. An organiser who knows which attendees are new. A structured way to meet three people before lunch. And a schedule with enough space in it that a conversation started in the corridor can finish.
The underlying reason it matters: a conference that only serves people who already know each other stops replacing its audience, and an audience that is not replaced ages out. The events that ran for a decade are almost all events that took this seriously.
The four decisions that do the work
Programme. At least one talk on the main track aimed at people in their first two years, scheduled at a time nobody has to choose against it. Beginner tracks covers how those are pitched and why they are harder to write than advanced ones.
Introductions. Somebody whose job on the day is to introduce people to each other. It costs one volunteer and it changes the experience more than any other single item. Mentorship covers the more structured version.
Space in the schedule. Breaks long enough that conversations complete rather than being cut off by a room change, which is the practical basis of the hallway track.
Information before the day. What time to arrive, what the room looks like, what people wear, whether lunch is provided. Every one of those is obvious to a regular and unknown to somebody attending their first one, and answering them in advance removes most of the anxiety attached to arriving. That is the subject of attending a conference.
What newcomers actually find difficult
Not the technical content. Almost every account of a first conference describes the same three difficulties, and none of them is the talks.
The first is arriving. Walking into a room where everybody appears to know everybody is the single most reported obstacle, and it happens in the first ten minutes, before anything else has had a chance to go well.
The hardest part of a first conference is the first ten minutes of it.
The second is lunch, for the same reason at greater length. The third is the assumption that everybody else understood the talk, which is almost never true and is impossible to check without asking somebody.
What this rules out as a solution: a welcome email that says everybody is friendly. It is true and it does not help. What helps is a specific instruction, a named person, and a reason to talk to somebody in the first half hour.
Where the name comes from
Beginner tracks at Ruby events were sometimes named after the language rather than described, which is how a strand aimed at newcomers came to be called a Nuby track at more than one conference in the late 2000s. The naming is a small thing, and it did one useful piece of work: it made the strand sound like part of the event rather than a remedial class attached to it.
The same instinct explains why the better beginner talks are not labelled beginner talks on the schedule. A title that names the subject draws the people who need it without telling the rest of the room that this hour is not for them.
For somebody attending their first one
The practical advice is short. Arrive for the opening rather than for the first talk, because the room is easier to enter when everybody else is also standing around. Ask two people what they work on before lunch. Pick the talk on the thing already being worked on rather than the most advanced one. And leave one session unattended on purpose, because the corridor conversation is frequently the reason people come back.
The rest of this section takes those in turn: a first conference from arrival to leaving, the practical logistics, the hallway track, mentorship and learning Ruby for the language itself. For the other side of a first conference, standing up rather than sitting down, first-time speakers starts there.
Questions
What is a newcomer track at a conference?
A set of adjustments to the ordinary event rather than a separate strand: a talk or two pitched at people in their first two years, someone whose job is to introduce people, breaks long enough for conversations to finish, and clear information sent before the day.
Should beginner sessions run in a separate room?
Generally not. A parallel beginner conference removes newcomers from the main room, which is where the value of attending actually is, and it quietly signals that the real event is happening elsewhere.
What do first-time attendees find hardest?
Not the technical content. Arriving into a room where everybody seems to know each other, then lunch for the same reason, then the assumption that everyone else understood the talk. All three are social rather than technical, and the first happens in the first ten minutes.
How much of a regional audience is new?
Around a fifth of the room is typically in its first two years, which makes it a larger group than the most experienced band. A programme written entirely for the middle of the distribution leaves that fifth with nothing aimed at them.
Should beginner talks be labelled as such on the schedule?
Better not. A title that names the subject draws the people who need it without announcing to everybody else that the hour is not for them, and it spares the speaker an audience that arrived expecting something more advanced.