CppCon will be an onsite conference at the Gaylord Rockies<\/a> in Aurora, Colorado, so we are calling for submissions from presenters that can join us onsite.<\/p>\n Submissions open: XX April 2026 For a chronological view of all the key conference dates, refer to the\u00a0CppCon Timeline<\/a>.<\/p>\n You<\/em>. If you have something interesting to share with the C++ community about C++ then please consider presenting. Our goal is to create the best program that we can and we feel that there must be room for both seasoned presenters and new voices.<\/p>\n We want to present the best C++ sessions of the year every year, so are happy to accept sessions that have been presented at other conferences. (We have enough compelling tracks that this isn’t an issue, even for attendees that attended the other conference.) Because our Main Program sessions are recorded, we generally do not accept the same session if it was presented at a previous year’s CppCon, unless that session has been significantly updated.<\/p>\n All submitted topics should be about making attendees better C++ programmers. Submissions such as Java for C++ Programmers<\/em> are off-topic. (A submission such as What C++ Programmers Can Learn from Swift<\/em> could be considered.) Submissions unrelated to C++, such as time or stress management are also off-topic. Note that submissions about software design are candidates for inclusion in our Software Design Track if they are presented by recognized C++ “experts” and focus on techniques and examples using C++.<\/p>\n We are open to any topic that will make attendees better C++ programmers. Below are some ideas.<\/p>\n CppCon attendees tend to be software engineers with many years of experience from a wide diversity of industries. Talks targeted to beginning C++ programmers are on topic, but are unlikely to be well attended. (But see our Back to Basics Track<\/a>.)<\/p>\n Talks aimed at experienced C++ programmers that are beginners in a particular area (for example, functional, game, or embedded programming, or introducing a new library or language feature), can be compelling.<\/p>\n Platform specific talks may be accepted, especially if they present general concepts and techniques that are not limited to one platform or tool. The number of people who could use the subject of your talk is part of our review decision. Broad appeal is better than narrow appeal, but deep appeal is our real goal. The abstract should make it clear why this is a C++ talk.<\/p>\n Standard presentation sessions are sixty minutes long (including Q&A). We can accommodate half hour sessions and multi-session submissions. Note that multi-session submissions may be harder to accommodate. Please indicate your flexibility.<\/p>\n We will also have Lightning Talks<\/a>, but they need not be submitted in advance of the conference. We will share more information about Lightning Talks and other opportunities for Open Content<\/a> in time for you to plan your participation.<\/p>\n Accepted half and full session speakers will have their conference registration fee waived (one speaker per half session). If you are planning to submit a proposal, please do not register<\/em> for the conference at this time. You’ll be contacted with special registration instructions later.<\/p>\n Further financial assistance is available to accepted speakers presenting in person. Please indicate if you require financial assistance when signing up for our Submission Page on Speaker.Fish<\/a>. Details are provided on request of the Speaker Liaison<\/a>.<\/p>\n The success of your submission and even the success of CppCon as a conference depends on the quality of your title and abstract. A compelling title and abstract will result in your submission being accepted by the Program Committee, increased attendance at\u00a0the conference, and increased attendance at your session.<\/p>\n Writing good titles and abstracts is an art, but here are some guidelines likely to make your submission more compelling.<\/p>\nDates<\/h2>\n
\nSubmission deadline: XX May 2026
\nDecision notifications by: XX June 2026
\nProgram available online: XX June 2026<\/p>\nWho Should Submit?<\/h2>\n
Topics<\/h2>\n
\n
\n
Audience<\/h2>\n
Format<\/h2>\n
Speaker Registration<\/h2>\n
Financial Assistance<\/h2>\n
Submission Title and Abstract<\/h2>\n
\n
\n
\n
\n
\n
![\"IMG_0010\"](\"https:\/\/cppcon.org\/wp-content\/uploads\/2016\/05\/cat-300x225.jpeg\")
The primary cause of the issues that attendee surveys have identified is that presenters under-estimate how long it will take<\/em> to cover material. When you practice your talk in front of your cat, you’ll cover a lot of material quickly because your cat understands everything right away. Practice in front of a real audience–at work and\/or your local user group. You’ll understand from the looks on their faces and the questions they ask how fast (or slow) you can go. You’ll begin to get a feel for how much material you can cover in sixty minutes.<\/p>\n![\"Andrei](\"https:\/\/cppcon.org\/wp-content\/uploads\/2020\/04\/JTP_5143-300x200.jpg\")
There are a few approaches you can take for code-heavy slides. One is just to pause when one comes up. The programmers in your audience won’t need to be told to start reading the code. Another approach is to talk the audience through all the code before focusing on the important part. (This might help you trim out code that doesn’t need to be on the slide.)<\/p>\n