Join Newsletter

Submission Guidelines – YOW! Lambda Jam

Provide sufficient detail in your submission to enable the reviewers to understand your proposal and clearly identify what an attendee will gain from attending your session. You should include the following information in the following parts of the submission system:

Session Title Title of the presentation (please keep it brief and specific)
Abstract Explain what the talk is about in plain English in 2 to 3 paragraphs. Your abstract should provide enough details for the reviewers to understand and assess your proposal and potential audience members to determine what your talk is about.
Theme / Topic / Category The category that best represents your talk:

  • Language
  • Practice
  • Technique
  • Design
  • Algorithm
  • Concept / Theory
  • Case Study
  • Experience Report
Level Indicate the level / background of the audience your talk is aimed at. YOW typically is for intermediate or advanced level talks rather than novice level:

  • Novice (for day 1 tutorials)
  • Intermediate
  • Advanced
Session Type The type of presentation you are proposing:

  • Talk: Talks are a conventional conference presentation of 30 minutes including introductions and questions. They are conducted in a lecture format, providing a focused explanation on a single topic. Some talks are an introduction to a subsequent Workshop or Code Jam (see Combo below).
  • Tutorial – Full day tutorial on the first day of the conference for those that are new to functional programming.
  • Workshop / Code Jam:
    • Workshops take the audience through the technical details of a specific technology. They are smaller and more slowly paced than talks and leave plenty of room for questions and discussions. Workshops should provide the attendees with sufficient detail and references to get started on a new technology.
    • Code Jams are an opportunity for attendees to code using their favourite or a new FP language. Attendees will solve the Code Jam problem by writing code together, while being guided by the conductor of the Code Jam. The software requirements and expected background knowledge will be announced in the program, so that all participants can ensure that they are prepared to code right from the start.
    • Workshops or Code Jams are 90 minutes duration. They are NOT intended to be long form talks, participants should be hands-on right from the start. If a longer talk intro is needed, consider a Combo submission (below).
  • Combo (Talk + Workshop / Code Jam): Many talks provide an introduction to a topic that is covered in more detail in a Workshop or Code Jam. In a Combo, the talk introduces general concepts of a technology and might serve as an introduction to get people interested in the subsequent workshop or code jam. The workshop or code jam provides the in-depth hands-on details needed to use a technology introduced in the talk in practice.
Duration (in mins) The duration of your session:

  • 30 mins (Talk)
  • 90 mins (Workshop / Code Jam)
  • 120 mins (Combo)
  • Full Day  (Tutorial on first day)
Co-Presenters The details of any additional presenters (they must have a ConfEngine account).
Target Audience The roles / audience that will get the most benefit from this talk.
Session Prerequisite Detail what an attendee should know or do before attending or anything they need to bring to this session.

Does your talk assume knowledge of a particular language or tool or mathematics (for example Scala, Quickcheck, Basic Category Theory)?
Outline / Structure Of Your Session Explain in detail how your presentation will be structured, what methodology and technology you will introduce, what examples you will use, etc.
Learning Outcome Detail the learning objectives for attendees (what will they learn or take away from the talk?)
Slides Please provide a link to a slide deck you may already have on this or a similar topic
Video Please provide a link to a video recording you may already have on this or a similar topic
Links Please provide a brief overview of your technical and speaking experience and links to previous presentations, videos, papers or accolades. We are looking for both new and experienced presenters!

If applicable, also provide a description of any supporting material which you will provide before the conference and that we will distribute to all participants via the YOW! Lambda Jam website — this may be text in PDF format and/or code as a compressed file.

If there is any generally available material that attendees may use after the presentation to deepen their understanding of the presented topic, please list that material as well.
Session Requirements Detail any additional requirements or logistics you may need from the organisers
Labels List any keywords that will help the program committee and attendees categorise your presentation.

All talk, workshop and code jam submissions should assume that the audience has as understanding of the core concepts of functional programming and will have experience using one or more FP languages (such as Clojure, Elixir, Erlang, F#, Functional JavaScript, Functional Python, J, Haskell, Lisp, ML, OCaml, Q, Scala or Scheme). Attendees seeking an introduction to functional programming languages and techniques are strongly encouraged to take a tutorial on day one.

Nothing upsets an audience more than a speaker that stands on stage blatantly promoting his or her company, product or achievements. Please keep the content of your talk on-topic and do not use this speaking opportunity as a sales pitch.

Depending on the number of submissions or the content of your submission, the program committee may ask if you would be prepared to accept a different session length.

Submit Your Talk

(a ConfEngine account is required)

For more information or questions, please email [email protected].