Thank you for your interest in becoming a speaker at C++Now.
Every year we release a Call for Submissions for the main program..
Most C++Now sessions are 90 minutes long, but sessions can be either shorter (45 minutes) or longer (multiples of 90 minutes). For 90 minute or longer sessions, registration will be waived for one presenter. For shorter sessions, registration will be prorated.
Interactive and collaborative sessions are encouraged, as this is the style of learning and participation that has proven most successful at these events. Many sessions take the form of a traditional presentation with a slide deck and a single speaker, but other formats are encouraged and supported.
Lectures focus on a practitioner’s ideas and experience with anything relevant to the C++ community.
Tutorials are sessions at which instructors teach conference participants specific skills or knowledge relevant to C++.
Workshops provide an active arena for advancements in C++-relevant topics. Workshops provide the opportunity for experienced practitioners to develop new ideas about a topic of common interest and experience. Workshops usually feature significant hands-on exercises.
Case Studies are reports on a particular project or projects that attempted something new and the results of the experience.
Panels feature several people presenting their ideas and experiences relating to C++’s relevant, controversial, emerging, or unresolved issues. Panels may be conducted in several ways, such as comparative, analytic, or historic and usually feature interaction between participants as well as Q&A with the audience.
Demonstrations show attendees what a particular process, product, technique, or library is capable of and how it is best used.
Other formats may also be of interest. Don’t hold back a proposal just because it doesn’t fit into a pigeonhole.
For more information about regular program submissions, contact the Program Chair: firstname.lastname@example.org
In addition to the main program we also have lightning talks. Lightning talks are only five minutes long. This is a challenging length for a technical talk! We make a Call for Lightning Talks a few days before the conference and continue to accept submission after the start of the conference.
For more information about lightning talks, contact the Lightning Talk Chair: email@example.com
All speakers must register to attend the conference.
Speakers that are speaking as Lightning Talk (only) presenters do not have their registration waived.
Regular program speakers have their registration cost waived. (Prorated up to one registration per full session.)
If your registration cost is waived, you will be contacted about how to register.
Please let people know that you are speaking! You are the attraction for this year’s conference, so let people know on Twitter (#CppNow), Facebook, LinkedIn, Slack, or where ever is appropriate for you.
Please join the Slack #speakerscorner channel by first using the auto-invite page for the CppLang workspace. This is a good way of asking questions of and getting advise from experienced presenters at C++ conferences.
If possible, give your talk before a live technical audience. Do it at work and/or with a local user group. You’ll be surprised at what you learn about how long it takes, what you find yourself wishing you’d included, and what questions you get. Pay attention to these issues, learn from them, and incorporate them into your talk. It will improve every time you give it, try to give it as many times as you can arrange an audience.
Please be prepared for questions. The C++Now audience is made up of seasoned software engineers with an advanced level of understanding of C++. It is also an audience that expects presenters to be ready, willing, and able to address non-trivial questions during a session. The environment is collaborative. The audience doesn’t want to see you fail and isn’t trying to play “Gotcha” or “ISO Standard Trivia,” but they do expect their questions and suggestions to be taking seriously.
There are two important reasons to repeat questions. One is that, even if you can hear the question, others may not. They may be seated behind the individual asking the question, so the questioner is facing away from them. Even if everyone in the room can hear the question, it may not be picked up well on the recording. You have a microphone; your version of the question will be clear.
So, if the questioner has a microphone, you don’t need to repeat the question, right? Wrong, because there is another reason to repeat the question (in your own words) and that is to let the questioner and the audience know what you thought was asked. Sometimes it isn’t clear what the questioner is asking. Time spent clarifying a point that was already clear is wasted time. Putting the question in your own words allows the questioner to say, “No, what I’m asking is…”
Not only does it work better to put the question in your own words, it may be smoother to just incorporate the question into the answer. “Yes, we could use a lambda expression here.” This works even if it is a comment rather than a question. “Correct, it would be wrong to use ‘unsigned’ in this case.” “Good point. It would be harder to understand this syntax if we weren’t using East const.”
It isn’t uncommon for content to take longer to deliver than you expect. This is part of the reason that we urge you to practice before a live technical audience. We aren’t so tightly scheduled that (with one important exception–see Half Sessions) you can’t go over by a minute or two. But do not go beyond that.
If you find that questions are taking you beyond your allotted time, you may cut them off by saying that you’ll continue to take questions during break.
You may feel that, since you were speaking before the lunch or dinner break, that you are free to run long. That is not the case. The audience, the volunteers, and the camera operators are all within their rights to expect you to end when you agreed to end. To not do so is rude and unacceptable.
The volunteers have been instructed to cut you off, but they really don’t want to do that. It is awkward for everyone. Practice your session, watch your time, skip the digressions if necessary, and end on time.
If you are scheduled to deliver a half session, your help is needed to make the program run smoothly.
If you are giving the first half session, arrive at your session extra early because not only will you need to get your AV setup and checked, the following presenter will need to be setup and checked as well. Please let the following speaker get set up and checked before you, so you’ll be setup and ready to go for your talk.
It is very important that you start on time, so that you be able to finish on time. Finishing on time means finishing with questions as well. You need to be off-mic and unplugged at the end of your allotted time so the following speaker will have their full time to present. If you want to offer to take more questions outside the session, please say that you’ll be available after the next speaker is finished, not during that speaker’s session.
If you are scheduled for the first of a pair of half-session talks, you cannot go over our time. You must stop when your time is up. There are no exception to this, even if your sessions started late through no fault of your own.
If you are giving the second half of two half session talks, arrive early before the session before yours starts. You need to be checked out on AV before that other speaker is setup for their talk. Since you need to allow at least ten minutes for the other speaker to be setup, you need to arrive in time so that you can be finished being setup (including necessary troubleshooting) at least an hour before your session is scheduled to begin.
It is understandable that right before speaking you might be too nervous to sit quietly through their talk (although that might help calm your nerves). If you can’t avoid pacing, please slip out of the session, but not far away. You’ll need to be available right after the previous speaker finishes to get set up and going.
Better safe than sorry: Your laptop may break or go missing. Consider:
Bash is company that records, edits, and uploads our videos. Here is their advice to presenters.
Here is Scott’s take on presenting code from his 2014 keynote at Meeting C++. (Thanks Jens.)
Here is a page of advice from the organizer of the Meeting C++ conference and user groups.
If you have any questions, please contact the Speaker Liaison.
We’ll see you in Aspen!