Title is evocative and short, but not too cute. If in doubt, keep it brief and descriptive.
The description succinctly sets out the problem the talk addresses, and what attendees will learn.
The abstract provides additional concrete details on what will be covered
New analysts or engineers are often lost when textbook approaches fail on real world data. Drawing inspiration from problem solving techniques in mathematics and physics, we will walk through examples that illustrate how come up with creative solutions and solve problems with big data.
TIP: Outline approach/bullet points is preferable to a long ramble
- •Creating Models
- •Sampling & Approximation
- •Finding Edge Cases
- •Testing Extremes
- •Working Backwards
- •Joining to External Data & Crowdsourcing
- •Turning Errors into Improvements
The title embodies why anyone should care about a new programming language
The description elaborates why the audience should care.
TIP: Descriptions are also a good place to describe what attendees will learn.
The abstract contains more specific details and demonstrates deep knowledge of the topic.
The computational kernel approach provides extreme performance, but sacrifices generality and assumes a fixed set of highly reliable computational resources. The framework approach gives up raw performance in exchange for fault tolerance, easier scaling, and greater generality. Julia provides a global distributed address space, a flexible futures mechanism, automatic serialization of user data and code, elastic parallelism, and simple, integrated fault handling. These primitives allow various approaches to distributed computation to be implemented succinctly and easily, with high performance, entirely in Julia.
Case Study Presentation
The title references a brand people have heard of and states clearly an attractive achievement with the promise of telling attendees how it was done
The description is clear on what attendees will hear: a fun and useful case study with specific and relevant lessons for others.
The abstract makes it clear that the speaker intends to convey transferable knowledge—always a concern with case studies, which are only entertainment if you can't get anything out of it for your own use.
If you are planning to build and launch a web application, growth is what you should be concerned with and prepared for. So how exactly can you architect an application, without breaking the bank, while sustaining a snappy and compelling application experience across the scaling spectrum?
In this presentation, Frank Weigel will focus specifically on the data management challenges web application developers face, and provide criteria for selecting a data management model that will provide the scalability and performance needed to support massive growth. The presentation will also highlight the architecture of OMGPOP's Draw Something, an example of a game that was prepared for growth.
Title is straightforward.
Scope is clear and with a concise description of what will be taught.
What attendees should bring and what they should expect to leave with is clearly emphasized.
TIP: if the topic is deeply technical, a brief outline should be included.
We will discuss how to figure out what story to tell, select the right data, and pick appropriate layout and encodings. The goal is to learn how to create a visualization that conveys appropriate knowledge to a specific audience (which may include the designer).
We'll briefly discuss tools, including pencil and paper. No prior technology or graphic design experience is necessary. An awareness of some basic user-centered design concepts will be helpful.
Understanding of your specific data or data types will help immensely. Please do bring data sets to play with.
Many thanks to Jeff Bezanson, Wes Bos, Noah Iliinsky, Rachel Myers, Emily Nakashima, Stefan Karpinski, Peter Skomoroch, and Frank Weigel for allowing us to use their speaking proposal submissions.