This presentation by Shandor Shand Dargo offers practical advice on crafting compelling proposals for C++ and other tech talks, emphasizing the critical role of the review process. It outlines that while deep technical knowledge is valuable, the ability to clearly articulate the talk's focus, motivation, and practical takeaways for a specific audience is paramount. The speaker details key traits of strong proposals, common pitfalls to avoid (such as inappropriate length, broad audience targeting, or overt self-promotion), and strategies for continuous improvement. A core message is the importance of being prepared for rejection, viewing it as an opportunity for learning and refinement.
Summarizing a Tech Talk Proposal:
0:00 - The Goal: The speaker, Shandor Shand Dargo, introduces the topic of how to make C++ or any tech talk stand out during the proposal review process.
1:08 - Standing Out (The Only Real Way): While one might try to write a "recognizable" proposal (discouraged and only for "big fish" speakers), the effective way is to write a strong proposal.
1:42 - Beyond Deep Knowledge: Deep technical knowledge alone is insufficient and not always strictly necessary to give a good talk. The core requirements are knowing what you want to say and presenting it decently.
2:27 - Selling Your Talk: A strong proposal effectively "sells" the talk first to the organizers (reviewers) and then, implicitly, to potential attendees.
Your proposal should visibly convey a clear focus and your personal motivation for the talk.
Crucially, know what you want to talk about (not just possessing general knowledge) and why now. This "why" can be personal or derived from a work project, and a strong "why" resonates with reviewers.
Pay attention to making your ideas clear and well-structured within the proposal.
Crucially, articulate what attendees will learn and the practical ideas they can apply in their jobs or lives. The talk should be for the audience, not for the speaker.
5:21 - Key Trait: Adhere to Requirements: Different conferences have varied submission platforms, length limits, and formatting rules. Always check how your proposal renders after submission and edit it for clarity and readability for reviewers.
Too Short: Risks reviewers questioning your commitment or ability to judge the talk's content.
Too Long: Risks reviewers not reading it fully or perceiving a lack of conciseness or clear thought.
Key Takeaway: Find the right balance; if proposing a longer talk, specify where content could be cut for shorter slots.
7:51 - Common Pitfall: Broad Target Audience: Avoid trying to appeal to everyone (beginners, intermediate, seasoned developers) unless it's a keynote. Identify a specific target audience and ensure it aligns with the conference's focus.
8:59 - Common Pitfall: Promotion: Do not use your talk slot for product, library, or political promotion unless it is explicitly a sponsored session.
Past Programs (9:26): Review past conference programs, titles, descriptions, and outlines (from recordings) to understand what has been accepted.
Program Committees (9:57): Join program committees to gain insight into how others write proposals, read reviewer comments, and learn what factors lead to acceptance or rejection.
10:25 - Be Ready for Rejection: Rejection is a reality due to limited slots, similar topics, and the need for topic balance. However, rejected proposals can provide valuable feedback, allowing you to fine-tune your proposal or develop new ideas for future submissions.
11:19 - Conclusion: Pay attention to requirements and target audience, write a well-structured proposal with clear selling points, avoid promotion, and embrace continuous learning and the possibility of rejection.